Another upload/download speed issue
-
@Wayne-Workman A different computer with an image for that particular model. I don’t have a master image, just an image for all the different computers that I have.
-
@the_duke Ok so for these tests, you’re using the same model and same image, but different machines, right? Just want to make sure I’m reading it right.
-
@Wayne-Workman no…I first reimaged one of my custom built computers with its own image and it ran about 500 MB/min. I then tried one of our refurbished units with its own image, using the same network port and had an average download speeds of 4 GB/min.
Hope that clarifies it a lot
-
@the_duke Are the two images you tested with the same image? Are the two computers the same model?
I’m not trying to be dense, believe me.
-
@Wayne-Workman no, different computers, different images.
-
@the_duke Ok. The model that has higher transfer speeds, are those higher speeds consistent with this model no matter where it is on your network?
And, the model that has the slower speeds, are those slower speeds consistent with this model no matter where it is on your network?
-
@Wayne-Workman correct
-
@the_duke Alright then. My suggestion is to change the FOG_PIGZ_COMP to 6, and then download each of your images, and then re-upload, without ever letting the image boot. meaning, as soon as it’s done downloading and reboots - just turn off that computer, and then setup an upload task and re-upload.
I think the compression settings may be your problem. Even if they aren’t, this change will dramatically speed up both uploads and downloads.
If we don’t see a dramatic transfer rate increase after this, I’m going to say we need to work on better supporting the NIC chipset that the troublesome model has.
-
@Wayne-Workman I will try this…I do have one issue with that sequence though, I run deepfreeze on my windows systems and it needs a reboot in order for it to work properly. If I don’t do that part right, I get an error when it is setting up windows. I’ll try it though to see what it does.
-
@the_duke Do whatever you need to do to make a proper image.
The way I suggested is the fastest way and assumes no changes to the image contents are necessary.
-
-
@the_duke Ok, well the good news is that the upload time was cut in half and the speed went from about 1.6 GB/min to 2.8 GB/min. The bad news is that it starts off great for a minute or so and now it is at 16% and doing 700 MB/min and continuing to drop. I just don’t see why it would all of a sudden in the last month or so. The only thing that I have had to change is we had a laptop that needed the ipxe.kpxe boot file to run and I had tried to use a different kernel before I changed the boot file, and I’ve changed it all back.
-
@the_duke Uploads are always slower. Be patient and let it finish first.
-
@Wayne-Workman No, I mean that the upload finished in about 11 minutes at an average of 2.8 GB/min. The download started off good for a minute or so and is now at 570 MB/min, has been running for over 18 minutes and still shows over 33 minutes left to go; at 35% on progress bar
-
@the_duke Your using the new inits. It’s totally possible that there is some fluctuation in upload times.
What I’m really curious to see is how download performs with the new image.
-
@Wayne-Workman Ok, I played around with a couple of other kernels and am now getting better download results so far with Kernel - 4.1.0 TomElliott. By better I mean it is so far doing about 24 minutes instead of the 1 hour as before. I’m trying different kernels right now to see if I can get it any better. I’m just guessing at this point.
-
@the_duke I’m pretty sure the kernel update feature would overwrite the inits you downloaded earlier. You’ll want to get those again after each different kernel download for testing.
-
@Wayne-Workman oh ok
-
@Wayne-Workman Ok, after trying several download tasks, I’m still getting nowhere. What had been taking 10 minutes at the most a month ago is now taking over an hour. Something has got to give…do I just need to try and reinstall fog or what’s the deal?
-
@the_duke Well your using better compression settings, better inits, and the exact same 1.2.0 code base, and Your only experiencing this issue on a particular model of computer, the location/port doesn’t make a difference, and this is a recent thing.
Those facts don’t compliment each other, not in my mind.
You could go ahead and rebuild, but I doubt that any change on the server would effect it since the problem is specific to a particular model of computer.
I’d say don’t change anything else on the server - don’t make any more changes to the kernel or inits or any of that.
Just play with changing the boot file - that’s it. See how that goes.
