EA V16 EAPX vs QEAX performance

[Ian Mitchell]

This is not a question - just an observation.
I've been testing some addins, using a variety of old repositories as test data.
And got confused about the results.
After a frustrating day, I finally found out that there is a big, and I mean BIG, HUGE, difference in the performance of EA 16 with QEAX vs the old EAPX format.
A factor of 20 - 50x !!
So if you are wondering why EA 16 is going slow with your old EAP files, just migrate them, and get an instant benefit.
Note that this is for Addins which use the API, so you ight not see the same effect using the UI.

[Paolo F Cantoni]

This is not a question - just an observation.
I've been testing some addins, using a variety of old repositories as test data.
And got confused about the results.
After a frustrating day, I finally found out that there is a big, and I mean BIG, HUGE, difference in the performance of EA 16 with QEAX vs the old EAPX format.
A factor of 20 - 50x !!
So if you are wondering why EA 16 is going slow with your old EAP files, just migrate them, and get an instant benefit.
Note that this is for Addins which use the API, so you might not see the same effect using the UI.

Well, Ian, this is a bit f a quandary.  We found the exact opposite!  As mentioned previously, our 15 min project transfer for snapshotting used to take 15 mins to create a 2 Gb file.  The QEA version takes 2 hours to create a 2.25 Gb snapshot!  We had to move to QEA files because of the 2 Gb limit or EAPX files.  Also, the few times we've had to use the QEA files via the App, it seems slower.

Paolo

[Ian Mitchell]

I thinks we may be comparing apples with...beer.
I was doing lots of simple operations through the API, not doing big data transfers.

[Paolo F Cantoni]

I thinks we may be comparing apples with...beer.
I was doing lots of simple operations through the API, not doing big data transfers.

You may be right, but I note that when the transfer has errors, it behaves as "a shirtload" of small API calls - since each row can be managed.


Paolo