Skip to content
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

Batching with types from another test classes. #25

Open
leo-gan opened this issue Jul 27, 2015 · 2 comments
Open

Batching with types from another test classes. #25

leo-gan opened this issue Jul 27, 2015 · 2 comments
Assignees

Comments

@leo-gan
Copy link
Contributor

leo-gan commented Jul 27, 2015

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.

@itadapter
Copy link
Member

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)

@leo-gan
Copy link
Contributor Author

leo-gan commented Jul 27, 2015

Дима, все наоборот. EDI - именно на месте. Просто хочется протестировать
для батчинга ObjectGraph, Telemetry, т.е. классы которые тестируются сами
по себе. А тут пусть все эти классы протестируются еще в режиме батчинга.

Regards,

Leonid Ganeline
Microsoft Integration MVP (BizTalk Server)
http://geekswithblogs.net/leonidganeline/

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants