There really is no trick, its just the expense of the license. If you have the correct license, witango will automatically bind to all processors, real or logical, and it does a good job of spreading its threads among the processors.

There are a couple of schools of thought...

Less servers, more processors, or more servers, each with one processor.

The better setup depends on your type of code. Is your application more process dependant, or throughput dependant? If you have a lot of calculations, and loops, the multiple processor approach, will probably serve you just as well, but if throughput is more of a concern, and it is for me, IMHO, you are better off with fast single processors, and great INTEL gigabit cards, with a super fast switch, and 1 or more db servers.

Because on multiple processor systems, you still only share 1 of the rest of the hardware, like the memory, network, etc.

If you are on linux, it is not so big a deal, cuz it doesn't seem to bog down like windows does, as long as you have enough memory. But windows, it bogs down, and you lose the througput, at least in my experience.

-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On Aug 2, 2006, at 12:30 PM, Wolf, Gene wrote:

   Thanks Robert. I will check out the Witango site to find any messages I can for setting this up but it seems to me with dual core CPU's becoming commonplace and now multiple dual cores being readily available, it would be very useful for Witango to provide specific instructions on how to set up 1, 2 and 4 CPU boxes or single and dual core cpu's and also how to set up multiple boxes to take best advantage of the cpu's. It seems really unreasonable to expect someone new to Witango to have to pour through the Witango mail list archives to figure out how to do this.
-----Original Message-----
From: Robert Garcia [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 02, 2006 3:00 PM
To: [email protected]
Subject: Re: Witango-Talk: Setting up multiple Witango boxes

I missed the last line, after the image, if you have professional licenses, you should be able to use dual core on each, with will give you a load group of 4 witango servers, and so you will have to have the 2 on the same servers, point to different ports, which makes it a bit trickier, but doable. Unless the professional license will allow you to set processor affinity to ALL, then you will have just 2 witango servers, taking advantage of all cores, which, IMHO, would be the best setup.

-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On Aug 2, 2006, at 11:50 AM, Wolf, Gene wrote:

I know a number of you have done this but I can't seem to find any instructions on doing this anywhere. We are outstripping our current hardware as we grow and slowly transition to another language. We need to gain capacity for processing Witango queries and plan on getting two new servers, dual core, strictly for processing Witango requests. I have two questions:
 
   1. Can Witango currently take advantage of dual core processors and
   2. Are there instructions anywhere that someone can point me to explaining how to set up an environment similar to the following:
 
<2006-08-02_14-43-44-069.png>
 
 
   If anyone can direct me to instructions, and offer pitfalls to watch out for I'd greatly appreciate it. Thanks!
 
   Oh, we will be using Witango 5.5 professional on each Windows server box. Yes, we're planning on purchasing 2 additional licenses. *grins*

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to