Category archives: Snaking

Discussions of programming, particularly of programming Python

RSS feed of Snaking

I want to play! (Gentoo calls... gosh that's geeky)


The ping scanner is getting pretty close. It now throttles the group-going-offline messages to 1 every 90s (otherwise you get 90 messages in about 5 minutes) and has around a 5 minute delay before the messages start after the groups go offline (depending on the size of the groups). 90s of that is just to ...

Continue reading

I want to play! (Gentoo calls... gosh that's geeky)


The ping scanner is getting pretty close. It now throttles the group-going-offline messages to 1 every 90s (otherwise you get 90 messages in about 5 minutes) and has around a 5 minute delay before the messages start after the groups go offline (depending on the size of the groups). 90s of that is just to ...

Continue reading

For those of you following along with the home game (When spec meets reality part LXVIII)


Wondering what all the silence on the Cinemon side is? Well, just me quietly pounding my head against the ping scanner. Still getting occasional PyPgSQL crashes, but I'm basically chalking those up to the number of threads trying to use PyPgSQL simultaneously.

For those of you following along with the home game (When spec meets reality part LXVIII)


Wondering what all the silence on the Cinemon side is? Well, just me quietly pounding my head against the ping scanner. Still getting occasional PyPgSQL crashes, but I'm basically chalking those up to the number of threads trying to use PyPgSQL simultaneously.

Scanner has been simulating for hours now (No memory leaks, and no crashes evident)


But at the current settings it could be as much as 20 minutes (in a worse-case scenario) before the scanner notices an offline low-level branch. It's currently taking ~4% of CPU, so I can likely rachet up the maximum group-ping frequency to 5 minutes or so and still have acceptable performance. Will need to work ...

Continue reading

Scanner has been simulating for hours now (No memory leaks, and no crashes evident)


But at the current settings it could be as much as 20 minutes (in a worse-case scenario) before the scanner notices an offline low-level branch. It's currently taking ~4% of CPU, so I can likely rachet up the maximum group-ping frequency to 5 minutes or so and still have acceptable performance. Will need to work ...

Continue reading

Harvest moon over Toronto this evening (Once in a while I glance up from the computer...)


Looks as though the problems with the scanner were being precipitated by having too many simultaneous postgresql queries. Introducing more randomness into the scanner has let it run for a few hours at a time so far. Have begun producing a trivial summary/overview in simple text which makes it possible to confirm that the scanner ...

Continue reading

Harvest moon over Toronto this evening (Once in a while I glance up from the computer...)


Looks as though the problems with the scanner were being precipitated by having too many simultaneous postgresql queries. Introducing more randomness into the scanner has let it run for a few hours at a time so far. Have begun producing a trivial summary/overview in simple text which makes it possible to confirm that the scanner ...

Continue reading