Re: firefox eats threads

[David Laight <david%l8s.co.uk@localhost>]

On Wed, Mar 18, 2015 at 05:17:29PM +0000, Eric Haszlakiewicz wrote:
> 
> 
> On March 18, 2015 11:01:15 AM EDT, Tobias Nygren <tnn%NetBSD.org@localhost> wrote:
> >Firefox names all it's threads by type with pthread_setname_np(3).
> >The following command is useful to find out what kind of threads are in
> >use:
> >
> >$ ps -sp 12501 -O lname
> >
> >Firefox after startup pools 45 threads so that's one third of your
> >available LWPs. My opinion is that the default ulimits on amd64 have
> >not
> >caught up with the times. 1024 would be a more reasonable figure than
> >128 & 160 for open files and lwps.
> >
> 
> Fwiw, chrome/chromium fires up 69 threads, although I've only examined it running on a linux box.
> Those limits are clearly inadequate.  They should probably be calculated based on the machine resources, such as the amount of memory available.

The 'hard' ulimit values also need reducing.

But yes, most of the 'system wide' limits (even processes for root)
could be usefully replaced my checks against free kva, swap and physical
memory.
The problem is picking the values.

Look at what MAXYSERS does :-)


	David

-- 
David Laight: david%l8s.co.uk@localhost