{"thread":{"id":"6403","subject":"gitk memory usage","startedAt":"2007-01-16T15:49:54Z","lastAt":"2007-01-16T15:49:54Z","messageCount":1,"participants":["Julian Phillips"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"31827","messageId":"Pine.LNX.4.64.0701161543260.19083@reaper.quantumfyre.co.uk","threadId":"6403","inReplyTo":null,"subject":"gitk memory usage","fromName":"Julian Phillips","fromEmail":"julian@quantumfyre.co.uk","sentAt":"2007-01-16T15:49:54Z","receivedAt":"2007-01-16T15:49:54Z","isPatch":false,"sender":{"key":"julian@quantumfyre.co.uk","avatar":"https://avatars.githubusercontent.com/u/948888?v=4"},"body":"\nI wanted to have a quick look at the commits that had been made on a \nparticular branch, and rather than use git log I thought I would try gitk.\n\nI was rather surprised to find that after running \"gitk \n<start_of_branch_tag>..<branch_head>\" (which showed a grand total of 4 \ncommits) wish had a virtual size of ~1.1G - which on a machine with 1G \nphysical RAM is not a good thing.\n\nDoes anyone know if this is to be expected from a large repository (~2.5G \npacked), or do I have a buggy version of wish installed?\n\n-- \nJulian\n\n  ---\nGet Revenge!  Live long enough to be a problem for your children!\n"}]}