-
Notifications
You must be signed in to change notification settings - Fork 6
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
Do we understand the performance of UDA? #39
Comments
Out of curiosity, checking the same in my local IMAS/UDA server. Difference is about 10 times.
software versions:
Info for the ones that haven't checked what IMAS_LOCAL_HOSTS does: it removes uda backend and sets the backend from the uda arguments. That's why the first and second calls are in fact identical. (access-layer/lowlevel/al_context.cpp#192) |
@cenkoloji -- How big were the IDSes you accessed? In my case Reading 48.138 MB of data for equilibrium/0 took 2.01 seconds using the "idssize" command of the soon to be released idstools (release/2.0.0) |
This example was just summary. I can't run idssize as the imas version I have isn't compatible yet. but summary and equilibrium IDS hdf5 files are around Repeating same exercise with both backend, using equiliibrium (I couldn't get mds backend to work via UDA)
|
I have been looking at the performance of UDA in getting an entire IDS -- in this case the summary IDS.
I have been using uda.py (https://gitlab.eufus.psnc.pl/data-access-tools/uda-test) for these tests.
The data resides at ITER and I have accessed it (1) directly from ITER using the UDA bypass feature, (2) using UDA at ITER talking to the ITER UDA server, and (3) using UDA on the EUROfusion Gateway talking to the ITER UDA server. The results are summarized below:
In all cases the command executed is
./uda.py -u 'imas://uda.iter.org:56565/uda?path=/work/imas/shared/imasdb/ITER/3/134174/117&backend=mdsplus' -c summary
Concentrating on the data "get" operation, we see:
Do we understand why accessing the data over the network is so much slower?
I also looked at a bigger IDS, and saw
Which gives:
The text was updated successfully, but these errors were encountered: