lp:meliae/0.1

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

116. By John A Meinel on 2009-12-23

It seems setup.py had a different idea of the current version.

Fix it so that it takes the value from meliae.__version__ instead.
And release 0.1.2, since 0.1.1 seemed to have already been taken.

115. By John A Meinel on 2009-12-23

Release Meliae 0.1.0-final

114. By John A Meinel on 2009-12-07

add some flush and close calls, as well as clearing out gc object lists.

This is in reference to bug #428165. I'm not positive that it fixes them,
but it should at least make it better.

113. By John A Meinel on 2009-12-07

Fix bug #493531 from James Henstridge.

112. By John O'Brien on 2009-12-02

Handle when there are fewer than 20 summaries.

111. By John A Meinel on 2009-11-20

When using dump_all_objects(), don't include the gc list itself.

110. By John A Meinel on 2009-10-27

make PerformanceCounter.get_timer() public.

Add a script to spawn a subprocess and watch its memory consumption.
The only thing this really benefits is 'mem-secs', the idea of how
many MB have been allocated for how long. This is slightly more
useful than peak memory for stuff like codehosting.
Since even if you peak very shortly, keeping the total memory consumption
lower gives you better concurrency.

109. By John A Meinel on 2009-10-27

Do a little bit to help ensure we don't get a deadlock.

108. By John A Meinel on 2009-10-27

Implement a PerformanceCounter module.

This allows us to track memory consumption, etc for a child process.
We might consider rewriting all of this as a pyrex extension. It would
probably provide a bit better performance, if it is something we are
going to be calling a lot. For now, this seems good enough.

107. By John A Meinel on 2009-10-23

pre-allocate the big dicts, if we are going to run out of memory, do it early.