How to make it FASTER
-
DOWNLOAD or UPLOAD or DEPLOYING an image…
How to make the process faster?
what factors should I check?
Disk speed?
network speed?
hardware specs? -
Also the compression listed on the GUI of the FOG dashboard. If you adjust the PIGZ compression to a lower number (less compression) the image will take less time to upload, it will take longer to deploy though.
What speeds are you seeing with Unicast that makes you feel as if FOG could be faster?
It’s VERY dependent on network gear too, are you using managed or unmanaged switches?
Have you followed the Cisco programming guide in the tutorials section if you have Cisco switches to see if your settings match that which are recommended?
We can’t make a recommendation for EVERY network set up in the world but we sure will try!
-
what will be the recommended hardware specs to have an overall better performance?
I’m more concern on fast deployment…
what I have now is just :::
i3 processor
16G ram
500G HDD
Dlink DIR-300 routerServer2008 as DNS and DHCP on VirtualBOX
Ubuntu server 12.04.5 LTS on VirtualBox also where I installed FOG 1.2.0
Windows Image on VirtualBox alsoWhat do you recommend ? do I need to change hardware specs? network gear?
I just have one computer to use, so I’m building the server via VM.
-
Prince,
While I assure you none of us mind helping, there are certain limitations to what we can help you with. If it’s problems with fog, please post them. Simple recommendations of things, sure. Your hardware specifications. I think that’s asking far too much as there’s too many variables to play with here.
-
ok I understand. Thank you
-
FOG doesn’t have any financial backing form big corporations so we don’t really have hardware specifications or recommendations
I can tell you my network is a Novell Netware 6.5 network, I don’t recommend Novell to ANYONE!!! And it’s not that the product is crappy, or the servers suck, its that when you fall behind you get left behind. It’s very hard to find anyone that services Novell in our area, let alone an out dated version. Now when we have problems and we contact any dealer, they look at our OS and they say “You’re OS is out of date, I’m sure that the latest update has fixed this issue for you, please update your server OS for further assistance”. Novell also has a really bad habit of selling off the management tools that they provide you with and this causes problems later, or stops supporting tools all together… I.e. ConsoleOne, iManager just to name a few.
I would, however, recommend some good switch gear. We use Cisco managed switches and Dlink managed switches. When it comes to labs most of the switches are Asus unmanaged gear, and for classrooms it is the same.
I would recommend at least gig speed equipment, if you have anything 10/100 base this could cause a bottle neck and has even crashed network gear.
As far as a server goes, FOG is linux based, that means the most mundane of machines can run this awesome technology. I would recommend using something at least Duo Core or higher, and of course lots of ram (2 or 4 gigs is more than enough).
I know this is really general, but FOG wasn’t built to ONLY run on AMD equipment, or ONLY intel equipment. It’s meant to be versatile so that even aged server equipment can suffice. I have in the past used our out going technology, but I quickly switched to some newer grade equipment (nothing spectacular, it would work as an AutoCad machine if I loaded windows on it, Duo Core Processor and 2 gigs of ram) and for my small imaging projects this server is quite the work horse!
-
So many ways to make things faster… disk/cache/storage nodes/switches/NICs.
I try to keep my image size down by using other tools that install some applications after imaging (if they’re needed on that machine)
the upside being that the machine can be in use while the applications silently install.
Would be nice to see if someone is using 10GbE or SSD or both.
Possibly also the new features involving clients seeding data to other clients in the latest SVN might make things a ton faster.
-
[quote=“VincentJ, post: 36948, member: 8935”]So many ways to make things faster… disk/cache/storage nodes/switches/NICs.
I try to keep my image size down by using other tools that install some applications after imaging (if they’re needed on that machine)
the upside being that the machine can be in use while the applications silently install.
Would be nice to see if someone is using 10GbE or SSD or both.
Possibly also the new features involving clients seeding data to other clients in the latest SVN might make things a ton faster.[/quote]
The capability to “seed” the files is there, but we have not yet included the installer. Nothing bad, just an add on that you will need to install a bittorrent client on the fog server for the “seeding” methodology to work.
-
[quote=“Jaymes Driver, post: 36925, member: 3582”]FOG doesn’t have any financial backing form big corporations so we don’t really have hardware specifications or recommendations
I can tell you my network is a Novell Netware 6.5 network, I don’t recommend Novell to ANYONE!!! And it’s not that the product is crappy, or the servers suck, its that when you fall behind you get left behind. It’s very hard to find anyone that services Novell in our area, let alone an out dated version. Now when we have problems and we contact any dealer, they look at our OS and they say “You’re OS is out of date, I’m sure that the latest update has fixed this issue for you, please update your server OS for further assistance”. Novell also has a really bad habit of selling off the management tools that they provide you with and this causes problems later, or stops supporting tools all together… I.e. ConsoleOne, iManager just to name a few.
I would, however, recommend some good switch gear. We use Cisco managed switches and Dlink managed switches. When it comes to labs most of the switches are Asus unmanaged gear, and for classrooms it is the same.
I would recommend at least gig speed equipment, if you have anything 10/100 base this could cause a bottle neck and has even crashed network gear.
As far as a server goes, FOG is linux based, that means the most mundane of machines can run this awesome technology. I would recommend using something at least Duo Core or higher, and of course lots of ram (2 or 4 gigs is more than enough).
I know this is really general, but FOG wasn’t built to ONLY run on AMD equipment, or ONLY intel equipment. It’s meant to be versatile so that even aged server equipment can suffice. I have in the past used our out going technology, but I quickly switched to some newer grade equipment (nothing spectacular, it would work as an AutoCad machine if I loaded windows on it, Duo Core Processor and 2 gigs of ram) and for my small imaging projects this server is quite the work horse! :)[/quote]
thank you…
I think my PC hardware is enough to run FOG server
I will try convince my boss to have our classroom lab a Gigabit network gears…
I cant tell if my test fog server now is slow or fast, since I didnt use any imaging server but FOG…
so why I ask how to make it faster? it is because I just want to maximize the power and usefulness of this awesome project…
Thanks FOG team
-
This post is deleted! -
the upside being that [COLOR=#ff0000][B]the machine can be in use while the applications silently instal[/B]l. [/COLOR]
what FOG tools is this?
-
[quote=“prince xyryl, post: 36956, member: 25316”]the upside being that [COLOR=#ff0000][B]the machine can be in use while the applications silently instal[/B]l. [/COLOR]
what FOG tools is this?[/quote]
I believe he is referring to the applications he installs himself, not a tool from FOG.
-
[quote=“prince xyryl, post: 36956, member: 25316”]the upside being that [COLOR=#ff0000][B]the machine can be in use while the applications silently instal[/B]l. [/COLOR]
what FOG tools is this?[/quote]
fog snapins allow you to install programs on the computer while it is running, though it takes a bit of practice with installers to make them work.
-
there are plenty of other programs to do this (silent application installs while pc is in use). I don’t use snapins in fog.
