Hi guys, It seems that we found the culpit, according to Igor advice I'm now measuring more and yes, ExternalSemaphoreTable is growing by one every snapshot, as Henrik already found out.
Few latest hourly reports: 0 HTTPCommections 5 Sockets 28 Processes 108 Semaphores 1 Socket registry 2 StandardFileStream registry 49 ExternalSemaphoreTable 0 HTTPCommections 5 Sockets 28 Processes 109 Semaphores 1 Socket registry 2 StandardFileStream registry 50 ExternalSemaphoreTable 0 HTTPCommections 5 Sockets 28 Processes 110 Semaphores 1 Socket registry 2 StandardFileStream registry 51 ExternalSemaphoreTable 0 HTTPCommections 5 Sockets 28 Processes 111 Semaphores 1 Socket registry 2 StandardFileStream registry 52 ExternalSemaphoreTable S, Igor Stasenko piše: > 2011/10/20 Janko Mivšek <[email protected]>: >> Hi guys, >> >> I'm measuring how my image is breathing through the time and what is >> interesting is how nr. of Semaphore instances is variating through the >> time. Every hour just before snapshot I report nr of instances, see last >> 10 hours: >> ** image state: >> 0 HTTPCommections >> 4 Sockets >> 20 Processes >> 300 Semaphores >> >> > Well, the number of semaphores tells nothing because not all of them > serve for sockets. > > There are 3 semaphores per socket. So, if you have 4 sockets, there > should be 12 external objects. > Of course not counting others, which is there for other purposes. > > Could you add following to report: > > Socket registry size > StandardFileStream registry size > (ExternalSemaphoreTable unprotectedExternalObjects reject: #isNil) size >
