[imapproxy] configuration advice [was :ImapProxy session issue ]

[Christopher Crowley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I am interested in opinions on a medium sized installation's
configuration. I haven't had a chance to test this yet, since I can't
generate the volume necesary to test it in a contrived situation, and
I am loathe to perform a "production test".  I plan to do so late one
night to see how performance is before imapacting the 11am rush.

I have about 6,000 unique users per day.  Peak concurrent usage is
1,200 sessions.  I currently have a seperate Solaris 9 box ready to
perform the imapproxy function, since previously imapproxy became
unresponsive when I put it into production.

My current config:

# keepalive and timeout values
keepalive       60
client_timeout  60
server_timeout  1800

# interval between stats messages, in seconds
stats_frequency 60

# maximum number of times a record can be reused. 0 means no limit
max_reuse       50

Christopher Crowley
TIS Network Services
Tulane University
ccrowley at tulane.edu
504.314.2535
PGP Key ID: 0x7CF18FDB

- ----- Original Message ----- 
From: "Eric Rostetter" <eric.rostetter at physics.utexas.edu>
To: "G G Papazoglou" <grp at med.uoc.gr>
Cc: <imapproxy at lists.horde.org>
Sent: Monday, January 13, 2003 6:02 PM
Subject: [imapproxy] Re: [imp] ImapProxy session issue


> Quoting G G Papazoglou <grp at med.uoc.gr>:
> 
> > > Not as long as you have a reasonable timeout on them.  If you
> > > set your time out too long, then yes, it could be a problem.
> > 
> > And what exactly could you mean by 'reasonable' ???
> 
> Well, first, if it is shorter than 15 seconds, then you are
> probably not going to get much advantage from the proxy.  So you
> probably want it to be in the 15-30 second range to get a decent
> performance increase. The max_reuse setting also comes into play
> here...
> 
> How large you can go depends on the number of concurrent users you
> have, and how many system resources you have.  Basically the larger
> the number of concurrent users, the smaller you need to set the
> timeout or max_reuse  settings.  And the less resources, then the
> faster you need to decrement it as the user base grows.
> 
> In other words: it is system dependent. :)
> 
> I've set the timeouts to 60 seconds, and max_reuse to 30.  It works
> for me, but my user base is small.
> 
> -- 
> Eric Rostetter
> The Department of Physics
> The University of Texas at Austin
> 
> Why get even? Get odd!
> 
> -- 
> imapproxy mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imapproxy-unsubscribe at lists.horde.org

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

iQA/AwUBPiSx180q7cR88Y/bEQIJgACghcyxsPsOlb3p1JMRgicPXDnQocYAniKY
qm0YmZwqKHkCujLIoYya99Rw
=yCGI
-----END PGP SIGNATURE-----