Best client distribution

**illmatik** · 09-11-2005, 10:42 AM

It seems like bandwidth and latency are the horsepower in the dimes world rather than cpu strength. I have 2 different broadband connections @ home. A 7meg down ~1mbit up cable connection and a 3meg down/768kup dsl line, and also have a neighbor's cable modem that he lets me use whenever I need some extra bandwidth. Do any of you know of a good traffic analyzer I can use to see which line I should stick my next agent on as I rebuild my home network, or does it not really matter? I have noticed my gf's P3-700 laptop running on 802.11b wireless card is putting up considerably less measurements than my p4 3.0 on the same network and it's ip is tagged high priority.

**[XC]thewildblue** · 09-12-2005, 12:34 AM

Hmm strange on the wireless and measurements. Im currently just using 2 lines, a 2mb/256k and a 512k/256.

I dont even think its down to latency or bandwidth, just sheer number of clients, as they all do a measurement at set intervals. Obvisouly if you were to have too many clients then bandwidth may become an issue.

**illmatik** · 09-12-2005, 04:21 PM

Oh cool. So I guess I can load more on to my dsl line which is my secondary line. The gf just uses the wireless on it to be able to surf from the laptop.

**Mr_Slinky** · 09-15-2005, 10:28 AM

Originally Posted by illmatik

Oh cool. So I guess I can load more on to my dsl line which is my secondary line. The gf just uses the wireless on it to be able to surf from the laptop.

i dont think you can have more then 1 instance running per machiene even if its got ht/dual core since its by connection and not cpu.

**[XC]thewildblue** · 09-15-2005, 10:42 AM

No your right you cant have more than 1 instance running per OS regardless of number of CPUs.

**illmatik** · 09-15-2005, 12:00 PM

Yeah, I was talking about clients as single physical machines and instances and how to distribute the load each dimes agent uses between 2 different switches on 2 different wans.

**Entity_Razer** · 09-17-2005, 11:03 AM

If you happen to have a rig which is capable of VMware ,install different OS's/virtuals and run them (Besides your MAIN os I'd run 2 more on a DECENT CPU, on a good one 3 or 4 more
depends on RAM actually

Ask TWB for more info on what comp can handle how many virtual machines

**[XC]thewildblue** · 09-18-2005, 12:25 AM

You would be surprised what a PIII450 and 256mb of ram can do.....hehe

**[XC] moddolicous** · 09-18-2005, 06:42 AM

Originally Posted by thewildblue

You would be surprised what a PIII450 and 256mb of ram can do.....hehe

What about a p2 & 24mb ram?????

**Helheim** · 09-18-2005, 07:44 AM

Is VMware better than Virtual PC?

**[XC]thewildblue** · 09-19-2005, 12:59 PM

I prefer VMware of virtual PC, but I havent really played with virtual for a long time.
Vmware is better with linux than virt PC.

A p2 with 24mb is good for just one client, try and dig out some more ram for that bugger !

**Entity_Razer** · 09-19-2005, 01:47 PM

RAM is life for a virtual setup.

Not so much mhz because I don't think your gonna work on it with like 3 diffferent OS's on a virtual machine so...

256MB ram minimum I reckon

**[XC]thewildblue** · 09-19-2005, 02:12 PM

Yeah 256 will run 3 setups but very slowly. Thats windows 2000, I couldnt get NT4 to work properly.

**Helheim** · 09-19-2005, 04:25 PM

How much RAM do you associate with each one? Does 2000 take less ram than XP? With XP I've been giving each one 128MB.

**[XC]thewildblue** · 09-19-2005, 10:12 PM

Im really tight on RAM allocation, when the host only has 256mb I assign each VM about 32mb. If I have more then they get 64mb. The best way to do it in my view is do an install with as much ram as poss. Then patch and get ready. Change swap file size early (I only give each vm a gig of drive space). Then make copies of this VM and start up each one separately, create a new ID for each and change PC name. Then once you have the required amount ready, change the Ram down to the minimum and power em all up. If you do each one in turn with new install etc it takes ages.

The quickest way to also install is to use an ISO image instead of a cdrom. So get your original CD and create an ISO from it. Then you can also install over your network if you like saving the need to get up and put a cd in a remote machine.

Hope that helps.

**InSanCen** · 09-19-2005, 10:38 PM

Originally Posted by thewildblue

Im really tight on RAM allocation, when the host only has 256mb I assign each VM about 32mb. If I have more then they get 64mb. The best way to do it in my view is do an install with as much ram as poss. Then patch and get ready. Change swap file size early (I only give each vm a gig of drive space). Then make copies of this VM and start up each one separately, create a new ID for each and change PC name. Then once you have the required amount ready, change the Ram down to the minimum and power em all up. If you do each one in turn with new install etc it takes ages.

The quickest way to also install is to use an ISO image instead of a cdrom. So get your original CD and create an ISO from it. Then you can also install over your network if you like saving the need to get up and put a cd in a remote machine.

Hope that helps.

Fancy doing a walk-through on that? I've never used VMWare, but have a friend who will donate me his Disc(s?), (They're Legit), as he no longer uses it.

I guess a dedicated DIMES box with XP2400, 512MB DDR & 20Gig would be okay soley for this purpose?

**IFMU** · 09-19-2005, 10:38 PM

TWB, may I suggest you do a little write up with details on how to do all this you are talking about?
I have 2 duallies here that both have 512memory that I can setup but to be honest, you pretty much lost me on most of what you said.
Cough up some details and explain how to do all this your asking to be done!

**[XC]thewildblue** · 09-20-2005, 12:38 AM

No problem once I get home from work tonight I will get started on it.

**IFMU** · 09-20-2005, 03:46 AM

Very cool!
Many thanks for your time!!!

**[XC]thewildblue** · 09-20-2005, 01:32 PM

Here is a quick guide on getting started.

Thewildblues VMware Quickstart Guide

Once you have installed VMware, start up the program and you will be presented with the following screen. From Here select create new Virtual machine.

Now select typical

Now choose you operating system of choice. Lets go with 2000 pro for the moment.

We now choose the name and location for our VMware OS.

You are now presented with your networking choice. For standard use I always use bridged.

**[XC]thewildblue** · 09-20-2005, 01:37 PM

You are now asked to specify the size to allocate. I choose 1gb as Im a tight arse. Ive never bothered with allocate now as Im too impatient to wait. It is tight on 1gb though.

Hey presto you nearly ready to go. Now double click memory to specify the amount for your virtual machine. When installing an OS I usually give as much as possible as it takes less time.
Once the machine is all installed you can tune it from there.

http://www.xtremesystems.org/forums/...id=37347&stc=1

Its as easy as this to allocate memory, just move the slider or enter the number.

I have found that I can run as low as 32mb for windows 2000.

Next double click CDROM. This is where you can choose you device of choice (if you have more than one drive) or instead choose an ISO image to install from. Once done click ok.

You are now ready to power up your virtual machine. Install your OS as per normal.

Once you click inside your virtual machine you are locked in there. To release the cursor press ctrl and alt together. Once you have installed your OS you can then install VMtools from the VM menu, install VMtools.

VMtools allows you to move around without the need to press ctrl alt to release the cursor.

To enter ctrl alt delete to log in you now use ctrl alt insert to login to a virtual machine.

Once you have created you VM machine go to the folder and copy all the files to a new folder.

Now start up this V machine and you are prompted if you want to create a new ID, select yes and also remember to rename the network name and IP address so it wont conflict with your previous machine. Once this has been done you can power up the original. You can repeat this as much as your machine can handle.

One thing to remember if you have specified a low disk space allocation, remember to adjust the swap file size accordingly as otherwise it will exceed disk space pretty quick due to having a swap file for say 256mb of ram. Also feel free to turn off as many unneccessay services as possible.

I wouldnâ€™t install Dimes until the last moment on each as otherwise you will have say 3 machines with all the same Dimes ID, which I donâ€™t thinks helps the points. Remember each dimes client will consume more bandwidth.

VMware can do quite a lot more from what I understand but Im not completely familiar with it as yet.

Hope this all Helps

James