Let's talk about all the matrices we have
[email protected] (Scott Baker) Thu, 22 May 2025 10:58:32 -0700
| Newsgroups | perl.cpan.testers.discuss |
|---|---|
| Message-ID | <[email protected]> |
--------------cnEn9wYpZlKtRZtM9PqvOjDY
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
CPT Folks:
The "primary" interface people use for CPAN Testers is the column matrix
view that shows configurations and test status. Currently we have three
matrices:
* http://matrix.cpantesters.org/?dist=Random-Simple%200.24
* http://fast-matrix.cpantesters.org/?dist=Random-Simple%200.24
* https://fast2-matrix.cpantesters.org/?dist=Random-Simple+0.24
The plethora of matrices sprung up from a time when the CPT web API was
not as reliable or fast. Earlier today matrix was spinning, while the
other two were working. A regular user will not understand the
intricacies of each one. What domain should a new user be using in 2025?
FWIW the "testers" section of MetaCPAN links to fast2 which seems to be
the most reliable currently.
I believe all three of these are run by Slaven and hosted on his
personal infrastructure in Germany? Is it worth maintaining three
separate matrices? Should we consolidate down t one? Slaven are you OK
hosting your matrixes yourself?
To add slightly more confusion to this discussion I've been working on
Perl-Magpie with Ruth that offers a modern matrix view for CPT data also:
* https://matrix.perl-magpie.org/dist.php?dist=Random-Simple
The goal for Magpie was to be super fast, and independent from CPT.
Magpie is a caching frontend for CPT and should work just fine even if
CPT is not accessible. Magpie pulls data using the CPT API, which it
then caches locally in PostgreSQL. This has the potential to reduce some
of the load on the CPT web servers because test results are served
locally. The primary usage of the CPT webservers is serving the textual
report content to users. This amounts to about 11 hits per second on the
primary web server.
Doug was working on getting the daily CPT emails working again. My
primary introduction to CPT was those emails, so I want to make sure
we're directing those people to the most reliable CPT we can. Same thing
with the linkage on MetaCPAN.
What matrix are you using today?
-- Scottchiefbaker
--------------cnEn9wYpZlKtRZtM9PqvOjDY
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>CPT Folks:</p>
<p>The "primary" interface people use for CPAN Testers is the column
matrix view that shows configurations and test status. Currently
we have three matrices:</p>
<ul>
<li><a class="moz-txt-link-freetext" href="http://matrix.cpantesters.org/?dist=Random-Simple%200.24">http://matrix.cpantesters.org/?dist=Random-Simple%200.24</a></li>
<li><a class="moz-txt-link-freetext" href="http://fast-matrix.cpantesters.org/?dist=Random-Simple%200.24">http://fast-matrix.cpantesters.org/?dist=Random-Simple%200.24</a></li>
<li><a class="moz-txt-link-freetext" href="https://fast2-matrix.cpantesters.org/?dist=Random-Simple+0.24">https://fast2-matrix.cpantesters.org/?dist=Random-Simple+0.24</a></li>
</ul>
<p>The plethora of matrices sprung up from a time when the CPT web
API was not as reliable or fast. Earlier today matrix was
spinning, while the other two were working. A regular user will
not understand the intricacies of each one. What domain should a
new user be using in 2025? FWIW the "testers" section of MetaCPAN
links to fast2 which seems to be the most reliable currently.</p>
<p>I believe all three of these are run by Slaven and hosted on his
personal infrastructure in Germany? Is it worth maintaining three
separate matrices? Should we consolidate down t one? Slaven are
you OK hosting your matrixes yourself?<br>
</p>
<p>To add slightly more confusion to this discussion I've been
working on Perl-Magpie with Ruth that offers a modern matrix view
for CPT data also:</p>
<ul>
<li><a class="moz-txt-link-freetext" href="https://matrix.perl-magpie.org/dist.php?dist=Random-Simple">https://matrix.perl-magpie.org/dist.php?dist=Random-Simple</a></li>
</ul>
<p>The goal for Magpie was to be super fast, and independent from
CPT. Magpie is a caching frontend for CPT and should work just
fine even if CPT is not accessible. Magpie pulls data using the
CPT API, which it then caches locally in PostgreSQL. This has the
potential to reduce some of the load on the CPT web servers
because test results are served locally. The primary usage of the
CPT webservers is serving the textual report content to users.
This amounts to about 11 hits per second on the primary web
server.</p>
<p>Doug was working on getting the daily CPT emails working again.
My primary introduction to CPT was those emails, so I want to make
sure we're directing those people to the most reliable CPT we can.
Same thing with the linkage on MetaCPAN.</p>
<p>What matrix are you using today?<br>
</p>
<p>-- Scottchiefbaker<br>
</p>
</body>
</html>
--------------cnEn9wYpZlKtRZtM9PqvOjDY--