deploy in multicast very slow with 1.5.10.1629 version
-
I installed developement 1.5.10.1629 version and tryed to do a multicast deploy on 4 identical pc.
The process is very slow on a gigabit ethernet network the speed is only of 1,09GB per minute.
There are changes in multicast deploy from 1.5.10 to 1.5.10.1629 version?
with 1.5.10 i can do imaging at full GIGABIT speed, with 1.5.10.1629 the speed is only 0,1453 GIGABIT… -
@fabritrento I am not aware of any differences in speed changes, though there is bandwidth limiting I capabilities. Pretty sure those capabilities exist in 1.5.10 as well though so the only real “change” I suspect are based on the kernel’s being upgraded and maybe something there changed.
-
@Tom-Elliott can you remove the bandwidth limitation? or put sliders on the web interface to decide the limit?
-
@fabritrento What I’m saying is I don’t think the bandwidth limitaiton stuff is what’s happening in your case. It’s been in there since 1.5.1 I believe, so this isn’t why you’re seeing slow downs on multicast.
This might be because of drivers in the kernel where as you stated you got full speeds with earlier versions of FOG. Try 6.1.22 kernel or something?
-
@Tom-Elliott how i can select the kernel version to be used in deploy or capture processes on pc?
-
@fabritrento FOG Configuration Page -> Kernel Update.
Most likely use the 64 bit kernel and just keep the filename set to bzImage and you should be good
-
I installed
Date:
Version:
Architecture:
March 31, 2023
6.1.22
AMD/Intel 64 Bitnext week i test newly a multicast process of 23pc togheter then i can compare the network troughput.
if speed is ok we can candidate 6.1.22 to stable fog release, otherwise we can rollback to fog 1.5.10 stable kernel version that i’m sure that are faster -
@fabritrento @Tom-Elliott with the kernel 6.1.22 developement the deploy/capture speed si faster, so plan to insert this kernel version as default on the next stable release
-
@fabritrento That’s not how this works. Just saying lol. 6.1.22 works fast for your situation, but that doesn’t mean there’s truly something wrong with the kernel for everybody. So when the next stable release comes out, you should remember to switch back to 6.1.22 and we’ll work to keep trying to update the kernels and hope that you’ll test them to see if it works for your situation so you don’t have to revert it to 6.1.22.