Hi,
Could anybody with good understanding of how STAF works under the hood give
a short overview of what happens when a static handle is created (how many
threads per handle etc.).
I'm working on a distributed testing framework that uses one central
machine to manage/schedule/run/log tests and each test can run on one or
more remote test nodes. I want to know if creating a separate handle for
each node for communicating with the central machine is something I should
consider. Right now we have one handle per test, which, while
computationally less costly, it adds unnecessary complexity to our system.
So, if it is not too expensive, I would like to make things simpler by
giving each node its dedicated handle.
Currently the max number of nodes simultaneously communicating with the
central machine is around 15 but it can eventually grow up to ~100. Would
100 long-running handles be a problem for STAF?
Regards,
Erik
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
