2MB Transfer over GBE | Fog 1.2.0
-
How does the http .iso download work? Does it download then mount it or is it try to unpack the .iso on the server?
-
it tries to store the iso into ram on the client.
-
So IO shouldn’t be a problem. The client in question has an i3 with 8GB of RAM. Do you have to do custom iso’s over HTTP or can you pull them from TFTP?
-
when loading an ISO into ram, the transfer method to get it there is irrelevant, as long as it gets there
-
Well, I’m trying to see what could be the issue. It shouldn’t be 2MB slow. Even on at 10/100 connection. I’m trying to see if another retrieval method would be faster.
-
Out of curiosity, could 2 NIC’s have anything to do with it?
-
One of the reasons to go http over tftp is the speed.
TFTP has this problem of limiting down to 10MB per second transfer, where HTTP can achieve, potentially, full throughput on the NIC.
Yes, 2 NICs could potentially cause issues though I don’t know how or what the issue is.
-
I have it running out off of the onboard NIC (Intel Controller) and it’s still 2MB. Is there anything I could paste to provide better information? I’m really stuck to why this is happening.
-
Is it bridged or host-only?
-
[quote=“Tom Elliott, post: 37978, member: 7271”]Is it bridged or host-only?[/quote]
It is host only.
-
Can you attempt putting it into Bridged mode.
Host-only, as I understand it, makes the device as if it’s going through the host machine. This sound’s like it’d be a good thing, except the VM still has to process the information as if it is its own device. So, when you choose Host-Only, the device suddenly becomes processed by two CPU’s.
It’s just a theory and one that I think deserves a good ol’ college try!
Change out of host-only to Bridged NIC and maybe things will work better?
