Re: [Psidev-ms-dev] mzML 0.99 remarks

[Brian P. <bri...@in...>]

Heap fragmentation has a performance cost that persists past the initial
allocation(s), since it affects further allocations as well.  If it can be
avoided with a relatively simple mechanism like this, that's a good thing.

I started coding in 1977, FWIW.  Long enough to learn to prefer the simple
solution over the one that requires a gestalt...

To be fair, having done this stuff for a long time isn't really a predictor
of me being any good at it, but I get by OK.

- Brian



-----Original Message-----
From: psi...@li...
[mailto:psi...@li...] On Behalf Of Mike
Coleman
Sent: Tuesday, October 09, 2007 9:21 AM
To: Mass spectrometry standard development
Subject: Re: [Psidev-ms-dev] mzML 0.99 remarks

I can see why having a 'count' might make it easier for novice
programmers to *write* a processing program, but I cannot see why
having a 'count' would make more than a negligible difference in
performance, if even that.  As a worst case, one could read the mzML
file into memory, scan it once to calculate the count, and then
proceed as before.  The additional time required to do a sweep through
RAM would be trivial.

Mike




On 10/9/07, Marc Sturm <st...@in...> wrote:
> I would like the count attributes to stay, at least for the spectrum
> list and peak list.
> Knowing the number of elements can make a huge performance difference in
> some languages e.g. C++.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Psidev-ms-dev mailing list
Psi...@li...
https://lists.sourceforge.net/lists/listinfo/psidev-ms-dev