On Fri, 10 Aug 2007, Martin Albrecht wrote: > > On Friday 10 August 2007, David Harvey wrote: >> Strongly agree. >> >> I'd like to add something. I consider "slowness" a bug. When SAGE does >> something obviously way too slowly, that's almost as bad as a genuine >> bug. Some slownesses are easy to fix, some are not. >> >> One of the things that really worries me is that someone who doesn't >> know the code really intimately, can change something in a way that >> they think improves the code, but that has a dramatic negative effect >> on performance in apparently unrelated areas. A common culprit is >> adding "type-checking" to the beginning of a low-level function. We >> currently don't have any systematic way of even *noticing* these kinds >> of things. >> >> It would be great if we had some coherent way of managing this. The >> first thing that occurs to me is some kind of "docprofile" (like >> doctests, but for checking speed of operations). If this works, it >> might be a good way of spotting "speed regressions". This is probably >> quite hard to set up.... for lots of reasons.... but I'm wondering >> whether people think something like this is feasible. >> >> david > > > Actually, after thinking about it: > > I would like to split this thread. > > Even though I like the idea of filing bug reports for things that are slow and > being conscious about speed regressions when fixing bugs, I would like to > focus on bugs in a very narrow sense for the first bug squashing event. A bug > in this sense is a command which returns an error message, a SEGFAULT or a > wrong result for something that is supposed to work. Those things leave a > quite bad impression and should be relatively easy to fix in general. > > Thoughts?
Yeah sure, I didn't mean to hijack the thread. The segfaults are obviously more important than the slownesses. I think your proposal is more likely to succeed if we don't get sidetracked :-) david --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
