-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profiling of CBF reading performances... #52
Comments
the current values is (for 200 Pilatus 2M images): Both astype and MD5 could be skipped when speed is really needed |
After simple optimization on reaches 1.8s. |
Hi Jerome, Vadim's code in cryio might be useful for doing a benchmarking Back in November 2014 we saw: In [23]: %timeit ret = cryio_cbfimage.CbfImage("run2_1_00148.cbf") In [25]: %timeit ret = fabio.open("run2_1_00148.cbf") I seem to remember that it was before some cif optimisations... On 21/03/2016 17:34, Jerome Kieffer wrote:
|
After optimization, reading of 200 files takes 1.17s (0.93s for the decompression and 0.09s for the read itself) In [14]: %timeit fabio.cbfimage.CbfImage().read("run2_1_00148.cbf") %timeit fabio.cbfimage.CbfImage().read("run2_1_00148.cbf", check_MD5=False) |
Hi
I may try to run the tests again, to compare it. Vadim |
On Mon, 21 Mar 2016 10:35:28 -0700
To be fair, run the test on scisoft13 ... now >90% of the time is spent in the "byte-offset decompression" Cheers, Jerome |
Requested by ID31 & ID15.
The text was updated successfully, but these errors were encountered: