You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now batching is performed for classes, created for this test. Only EDI class is created for EDI test and not for Batching.
I think Batching test is orthogonal to other tests, that means it rather uses the Typical Person, Telemetry, EDI, ObjectGraph test classes and does not use specialized Personal, Bank, Trading, RPC classes.
The text was updated successfully, but these errors were encountered:
I purposely added EDI into batching test - it is interesting to see how it performs (complex object graph).
Why not use it? If one doesnt need it - change in your config.
What I learned is that Batching benefits diminish with the increase of payload complexity (such as EDI)
Дима, все наоборот. EDI - именно на месте. Просто хочется протестировать
для батчинга ObjectGraph, Telemetry, т.е. классы которые тестируются сами
по себе. А тут пусть все эти классы протестируются еще в режиме батчинга.
On Mon, Jul 27, 2015 at 3:20 PM, Dmitriy@ITAdapter <[email protected]
wrote:
I purposely added EDI into batching test - it is interesting to see how it
performs (complex object graph).
Why not use it? If one doesnt need it - change in your config.
What I learned is that Batching benefits diminish with the increase of
payload complexity (such as EDI)
—
Reply to this email directly or view it on GitHub #25 (comment).
Now batching is performed for classes, created for this test. Only EDI class is created for EDI test and not for Batching.
I think Batching test is orthogonal to other tests, that means it rather uses the Typical Person, Telemetry, EDI, ObjectGraph test classes and does not use specialized Personal, Bank, Trading, RPC classes.
The text was updated successfully, but these errors were encountered: