Forum Discussion
Mar 01, 2010
I guess I'm still confused. Each thread will issue 100s of sequential requests to different pool members (thread 1: 10.10.1.1-100, thread 2 10.10.2.1-100, etc). If I have 100 parallel threads each issuing out sequential requests to different pool members wouldn't you eventually have one overlap of calls where more than one thread is making a call in the same millisecond?
And, it's not really my show since you brought up the issue.
BTW, I got a rough app built that will spin up a pool with 10000 members, spin up 100 threads each sequentially disabling different pool members. At the end of the loop, all 10000 pool members were disabled. Maybe I'm totally missing something. Next step will be to put out timer with each request to determine when the requests go out.
Another factor here could be that I'm running on v10.1 and this could be a platform specific problem. When I get my app flushed out, I'll pass the source along to you to test out.
-Joe