unreliability...

[David Miller]

Between the various bugs that have crept into patchwork during the
last sizable update (especially the add to bundle crashes that are
still unsolved), the often sluggishness of patchwork.ozlabs.org, and
the occaisional downtimes (it's giving internal server errors right
now as I type this) patchwork is starting to become unusable for me.

That's sad because I've become very dependant upon it to work
efficiently.

I'd like to see this improve, obviously, so what can we do about this?

Really, I use it heavily.  I'm often modifying states of 40 or more
patches at a time, making lots of searching on old patches which have
been applied or rejected or whatever.  I make 7 to 10 bundles in one
sitting and operate on them.

So I hit patchwork pretty hard and in particular performance for large
bulk operations is starting to become very important.

Also, is it just me or is patchworks getting slower as the number of
patches in a project's queue get larger?  Are there some scalability
problems related to the number of patches in the database?

Thanks!