http://nebula-rnd.com/blog/tech/2006/05/how-many-licenses-do-i-need.html Welcome to the Nebula Fri, 06 Jan 2012 09:44:06 +0000 hourly 1 http://wordpress.org/?v=3.1 http://nebula-rnd.com/blog/tech/2006/05/how-many-licenses-do-i-need.html/comment-page-1#comment-175 symeonb Tue, 27 Jun 2006 07:05:42 +0000 http://nebula-rnd.com/blog/general/2006/05/how-many-licenses-do-i-need.html#comment-175 Hi Tony - I just wanted to make a small comment on this. I have a great deal of experience in u2 systems servicing high availability high transaction web sites in the airline industry. Airlines do millions of bookings per month and millions of price quotes per day. A company called datalex have an air pricing engine that runs on U2 and that runs as phantoms that take requests to price via sockets (using GCI as was done before the u2 socket api). The processing is very processor intensive and has minimal disk i/o. We did some performance tests at the IBM testing centre in the UK and found that the optimum performance is to have a minimum number of u2 processes operating at a very high level of cpu. This was more performant than more processes with less cpu usage each. The optimum came at about 2 phantoms per CPU, which was TBH not something we had thought about. So in summary, as i think you have mentioned, it does really depend on what your app does, but also there are constraints and optimum parameters based upon the hardware architecture as well. Hi Tony – I just wanted to make a small comment on this. I have a great deal of experience in u2 systems servicing high availability high transaction web sites in the airline industry. Airlines do millions of bookings per month and millions of price quotes per day. A company called datalex have an air pricing engine that runs on U2 and that runs as phantoms that take requests to price via sockets (using GCI as was done before the u2 socket api). The processing is very processor intensive and has minimal disk i/o. We did some performance tests at the IBM testing centre in the UK and found that the optimum performance is to have a minimum number of u2 processes operating at a very high level of cpu. This was more performant than more processes with less cpu usage each. The optimum came at about 2 phantoms per CPU, which was TBH not something we had thought about. So in summary, as i think you have mentioned, it does really depend on what your app does, but also there are constraints and optimum parameters based upon the hardware architecture as well.

]]>