Replies: 2 comments 9 replies
-
Something is wrong if it’s taking that long. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Platform? Runtime? OS? Other information that may give a lead? This operation should be very fast on x86/x64 + coreclr. One possible reason can be that you are on blazor, xamarin or similar and not using AOT. |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My application currently contains a custom function based on the example at https://stackoverflow.com/questions/552467/how-do-i-reliably-get-an-image-dimensions-in-net-without-loading-the-image to extract the image size from a JPEG files. It can currently get an image size in <1 ms per file. I recently migrated from System.Drawing to ImageSharp, which generally went very well. Based on the documentation, I assumed that
Image.Identify
would do the job and that I'd be able to eliminate the code to read JPEG files manually. However, when I made that change, the time per image went up to a little over 60 ms, which is prohibitive. It would be great if ImageSharp provided a comparably fast function for this so that users don't have to implement custom JPEG reading code to get good performance.Beta Was this translation helpful? Give feedback.
All reactions