Krobar: do you know what the CPU usage is caused by? Reading from a single disk should be 1-3% cpu usage; somthing must be wrong in your particular setup.
That also counts for Samba; some don't even get 1MB/s on a gigabit network, some get 10MB/s, some get 100MB/s. For me, i tried tuning Samba but never gotten it to perform like NFS does; close to 100MB/s. Lots of times Samba is something in between 5-35MB/s. It appears this is an issue specific to Samba. It's one of the worst open source projects ever - so many years of development and still they cannot produce a simple filesharing service that simply works.
Samba is into all the "enterprise" stuff though. Me, i just want access to my files. Scr*w your active directory primary domain master whatever. I want access to file X and i want it now not tomorrow. A complete rewrite of Samba into a 15KB application that performs like it should, would be the best solution in my eyes. None of the current Samba devs should participate, or they'll f*ck this up once more.
Because of Samba performing so poor (especially on FreeBSD distributions), FreeNAS is also looking to migrate to the Linux kernel; all this because of one crappy software project.
@Krobar: what exactly do you mean with "BSD implementation of Samba"? Samba is a piece of sourcecode, it can be compiled on Linux and on BSD; still the same implementation. It just behaves differently on FreeBSD than on Linux. But Samba and performance problems go hand-in-hand; just google how much questions are regarding this.
That also counts for Samba; some don't even get 1MB/s on a gigabit network, some get 10MB/s, some get 100MB/s. For me, i tried tuning Samba but never gotten it to perform like NFS does; close to 100MB/s. Lots of times Samba is something in between 5-35MB/s. It appears this is an issue specific to Samba. It's one of the worst open source projects ever - so many years of development and still they cannot produce a simple filesharing service that simply works.
Samba is into all the "enterprise" stuff though. Me, i just want access to my files. Scr*w your active directory primary domain master whatever. I want access to file X and i want it now not tomorrow. A complete rewrite of Samba into a 15KB application that performs like it should, would be the best solution in my eyes. None of the current Samba devs should participate, or they'll f*ck this up once more.
Because of Samba performing so poor (especially on FreeBSD distributions), FreeNAS is also looking to migrate to the Linux kernel; all this because of one crappy software project.
@Krobar: what exactly do you mean with "BSD implementation of Samba"? Samba is a piece of sourcecode, it can be compiled on Linux and on BSD; still the same implementation. It just behaves differently on FreeBSD than on Linux. But Samba and performance problems go hand-in-hand; just google how much questions are regarding this.