Ruud van Meer wrote: > I could not find any information related to memory in the > manual/website. > > Has anybody got any clues on the memory usage of the sharity daemon on > Solaris 2.6? > How does this figure alter over a period of time with an increasing > number of mounts configured in Sharity?
You can find more information about this topic in the GUI application's help. Go to section "CIFS Servers" and select the help for "NFS File-Hanlde Lookup Strategy". The text is as follows: ------------------------------------------------------------------------- This is a setting for the NFS2 frontend. NFS relies on unique and for ever constant NFS file identifiers, which can not be provided by all backends. Sharity therefore has to manage these identifiers itself. There are currently two strategies for assignment of NFS file identifiers to files: the Table and the Pseudo-Inodes. The table-strategy is a strictly correct implementation, but it may need quite a bit of memory if you access a lot of files. As a rough estimate, it has to store 20 bytes plus the size of the filename for every file accessed. If you do a find over a large server, you can easily use up a couple of megabytes. This memory goes primarily on the account the swap file or swap partition. The pseudo-inode strategy is a statistical approach and can't guarantee correct lookup (although the probability for failure is very low) and it can't provide full Unix semantics for file renaming (Unix requires that a file's inode number does not change on rename or move; that can't be provided by this strategy). For the price of these disadvantages the memory consumption does not depend on the number of files accessed. It's not recommended to use the pseudo-inode strategy unless you have very good reasons to do so. ------------------------------------------------------------------------- The memory consumption is therefore proportional to the number of files you access, regardless of the number of shares you mount. If you don't access files for some time, the kernel will swap out the associated blocks of memory, freeing your physical RAM. Regards, Christian. -- Dipl.-Ing. Christian Starkjohann Objective Development mailto:[EMAIL PROTECTED] | http://www.obdev.at/ _______________________________________________ Sharity-talk mailing list [EMAIL PROTECTED] http://at.obdev.at/mailman/listinfo/sharity-talk
