If you'd mention your virtualization environment (as in xen, vitualbox, kvm…) that could help.
On a physical machine my opinion is that 512MB is fine for a linux OS + SBS. 256MB is a bit small I think. It all depends on what's loaded in the OS of course. A GUI will take a lot of RAM and disk space for itself. SBS seems to use around 200MB for itself. I have seen less. I have set the "performance" db settings in SBS preferences, recommended with > 1GB RAM. I guess it doesn't hurt. My DB files are as follows: library.db 29MB, persist.db 50MB, artwork.db 1.2GB (for comparison. I have no idea if this is relevant.) I am in the process of cleaning up my music library (for some time…) so it's down to 1200 albums and 16.5k tracks at the moment. I looked at my KVM machine, linux debian 6.0, no GUI, and was quite surprised to see it is set to use 2GB RAM. That's a lot, I don't remember any reason for such an amount. The swapspace is set to a more reasonable 256MB, and of course it uses none of that. The machine does very little besides running SBS, using a large swap makes no sense. A swap space larger than the amount of RAM is also IMHO of little use, unless you're ready to wait endlessly for the system once both are well in use. I use a compressed disk image (qcow2) but it has now fully expanded to the disk size, that is 3.5GB. The file resides on an SSD. The music files are on a ZFS pool, and shared by NFS. I use the virtio disk and ethernet paravirtualizing drivers, these do a lot of good if you're using kvm. ------------------------------------------------------------------------ epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711 View this thread: http://forums.slimdevices.com/showthread.php?t=96540 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
