[imp] horde/imp migration problems, cpu bound on solaris

[Vasilios Hoffman]

nope, it's a hashed directory structure for session_data, for example:

/usr/local/imp3.2/cache/session_data/3/9/sess_394bd2d80872323e03e3dd770974e5da

is one session file.  too many files in one directory slows down some
system calls (walking the structure in the inode becomes too expensive I
suppose).  we hash our /var/mail structure too, for what it's worth.
depending on the file system, driver, and system calls being made it may
gain you much or little.  At the least it should scale a bit better.

I don't trust solaris and ufs personally, they're stable but old-school.
I'm sure linux and something like reiserfs wouldn't have as drastic
penalties :)

-V


On Thu, 10 Apr 2003, Eric Rostetter wrote:

> Quoting Vasilios Hoffman <vhoffman01 at wesleyan.edu>:
>
> > < session.save_path = "2;/usr/local/imp3.2/cache/session_data"
> > ---
> > > session.save_path = /tmp
>
> I hope that is a typo???
>
> --
> Eric Rostetter
> The Department of Physics
> The University of Texas at Austin
>
> Why get even? Get odd!
>
> --
> IMP mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>