Fog Bandwidth Limitations
Running a 1gb network but the fog server is very sluggish. Version .32
it’s only using 20-25 mbps of the network. Any ideas?
[quote=“Jaymes Driver, post: 30645, member: 3582”]I hit 6 GB/min on 0.32… I have never seen anything image faster than that, but it could be my equipment.[/quote]
on this particular computer, it started at 7MB/min (probably caching and not actual transfer speed being represented here) and it never dropped below 6MB/min for the duration of the imaging process.
Running A PCI 10/100/1000/(125GigaBytes per second) NIC. Thank you guys. I believe I have my Solution!
[quote=“Junkhacker, post: 30565, member: 21583”]running fog 1.0+ i can image a single machine at 6+GB/min, if the client is fast enough.[/quote]
I hit 6 GB/min on 0.32… I have never seen anything image faster than that, but it could be my equipment.
running fog 1.0+ i can image a single machine at 6+GB/min, if the client is fast enough.
Using my nodes the fastest speed I got out of 30 dc7800 was 2.61 GB/min on part clone(fog 1.x.x). I have a 1GB fiber backbone with 1GB Netgear Switches.
I noticed that IDE hard drives operate much slower. SATA, SATA II. and SATA III all operate a also different speeds. I would say that yes the speed of cloning is VERY dependent on the hardware.
That will teach me to do conversions before coffee. Yes I should have come out with MB.
[quote=“need2, post: 30550, member: 21891”]A Gigabit network could transmit in the absolute best case scenario 125 gigaBYTES per second. [SIZE=2][/SIZE][/quote][SIZE=2] I think you meant to say 125 megaBYTES. So if everything was network limited and no compression, speeds would approach 7.5 Gigabytes per minute. [/SIZE]
[SIZE=2]1.2 gigabytes is reasonable for old clients (P4, IDE drives) on 0.32, I had a fully gigabit network a[/SIZE]s well[SIZE=2]. Fog in my experience is usually client CPU limited, because PIGZ is running client side. On FOG 1.1.1 with PIGZ_COMPRESSION set to 9, 6.9 gigabytes per minute on Haswell i5’s is standard for us (Dell Optiplex 3020’s). Going to experiment with the compression ratio to see if there is a speed up to be gained there. Hope that helps.[/SIZE]
The old version of FOG does not have as much in the way of compression, so it will consume bandwidth much more quickly.
If I read correctly that the server is a P4 with 4GB of RAM, then you are dealing a lot with processing speed, onboard bandwidth (speed of communication within the motherboard), RAM speed, drive speed, most likely a 10/100 network card, and the speed of the cache on almost every component previously mentioned all before the information can even leave the server.
Then it has to transmit over the network. Networks are measured in bps, or bits per second. A Gigabit network could transmit in the absolute best case scenario 125 gigaBYTES per second. HOWEVER, there are almost no cases where this happens. You have to deal with line quality (quality of the insulation and lines of the ethernet cable), distance degradation, switch performance, outside interference and other clients passing information before you even get to the workstation.
Finally, on the workstation, it has to process all of this information coming in over its ethernet card (also likely 10/100). The information has to go through a similar series of steps as to what it went through on the server but in reverse before it is committed to the drive, which most consumer class drives to not have amazing write speeds.
In conclusion, if you were to put FOG on a faster server, and/or upgrade to FOG 1.1.1, you should see a performance improvement.
I would Assume what ever is native to the fogging screen. I think its roughly 1.2 GigaBYTES per minute. It’s a single client or broken up into smaller chunks the more clients I add.
Pentium 4 4gb ram on ubuntu, download task
how many clients at once getting this speed?
what hardware is your server on?
also, is it megabits or megabytes of speed your meaning?
also, is this the upload or download task?
Please provide as much information as possible to allow people to help you