Log in

No account? Create an account

Wed, Jan. 20th, 2010, 04:43 pm
When my mind stop thinking, my eyes stop blinking

I just got back after 4 days away and had to deal with the morass of email, feeds, todo items and Tweets that had built up in my absence and it occurred to me that the way I deal with these datum is very much like how various Garbage Collection schemes work:

In general I use a Ref Counting system similar to how Perl does GC - I mentally keep a tally of how much external information is needed for an email and when that reaches zero I reply. This has the benefit of timeliness in much the same way a Ref Counted GC guarantees timely-destruction on scope exit.

The disadvantage is that, like Ref Counting, it's a lot of mental accounting and constant work to keep it under control. It tends to leak slightly so that the number of unhandled items slowly creeps up or some drastic event happens and it shoots up. In those scenarios I tend to do roughly the same as jwz  

"When my main Inbox folder hits 2000 messages, I sit bolt upright for 16 hours and cause it to contain less than 200

This is the equivalent of a stop-the-world mark-and-sweep GC a la older versions of Java and it's main disadvantage is it brings everything else in your world to a grinding, screeching halt - this is why Java apps occasionally lock solid: because a GC run has started and nothing can interrupt that.

I should probably start using a more modern scheme such as a Generational (sometimes known as Ephemeral) Concurrent Garbage Collector. This would mean that certain emails of different ages or priorities would be dealt with sooner and the rest when I have idle time. This sounds ideal except that it still requires an initial triage run and would also require much more sophisticated scaffolding for accounting and record keeping.

Thu, Jan. 21st, 2010 01:21 pm (UTC)
ext_222323: Profanesacheaufwendigetechnischemetapher

There must be an awesome German makeword for overly elaborate technical metaphors for mundane things.

I'm guessing this isn't it.

Mon, Jan. 25th, 2010 02:04 pm (UTC)

When my main inbox hits about 2000 items I tend to reboot the VM (aka "in:inbox" -> 'Archive'.) This has the advantage that an unknown number of things hit the floor, but the system becomes responsive again to new input very fast.