[arch-dev-public] Switching the bugtracker to Bugzilla

Florian Pritz bluewind at xinu.at
Wed Nov 15 08:52:34 UTC 2017

On 15.11.2017 09:07, Lukas Fleischer wrote:
> Generally speaking, I am in favor of setting up a fresh Bugzilla
> instance and not doing any sort of migration. The idea of switching to a
> new bug tracker came up at least four years ago and my feeling is that
> all this migration work is what was holding it back for a long time.

That's not really true. The most important problem back then was that
bugzilla only supported cgi and mod_perl. cgi performed really badly
when I tested it and mod_perl didn't perform much better because it just
hid the cost of compiling everything by using preforked workers. At
least until the pool of preforked workers was used up and it needed to
start new ones.

In the end the server was able to compile bugzilla roughly 8 times per
second using all cores and with a sufficient number of requests that
also seemed to affect mod_perl.

Nowadays bugzilla finally has psgi support where the perl code is
compiled once and requests are sent to it. At least without data this
leaves us with a few hundred requests per second so the base performance
is much much better.

Sadly it looks like the migration script, that once worked pretty well,
no longer works out of the box. Jelle has been working on reviving it.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 858 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20171115/027dd1e5/attachment-0001.asc>

More information about the arch-dev-public mailing list