I am looking into Rhino-esb and NServiceBus for a smart client application. I was doing some stress testing lately and I noticed some very strange behavior with rhino-esb. I tried to send large numbers of requests at the same time (6000-10000) and the memory of my back-end when using rhino-esb was continuously rising. I thought there was something with my code but memory profiling didn't show anything like that.
So I tried to stress the Alexandria application. I tried to send 6000 UpdateDetailsRequest requests within a for loop and the behavior was the same: after each batch 60mb of memory were "magically" lost (I have also a print screen from process explorer for anyone interested). I have even left the application running for quite a while (30mins) after these tests waiting for the memory to go down but no luck. I have to note that both the host and the client were running to the same machine. Am I using it wrong? am I expecting too much? Any help will be really appreciated. Thanks. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
