Front page | perl.perl5.porters |
Postings from December 2020
On 12/24/20 1:31 PM, Ricardo Signes wrote: > Once upon a time, a sponsor provided a server called dromedary. It was > a big beefy hunky of hardware with a lot of RAM and a bunch of cores. > It compiled perl very fast. Some people used it for bisecting, some for > testing a bunch of different versions of perl, and so on. > > Later, a second dromedary existed and was used, but less. > > I've been trying to get a handle on the various resources we rely on, > and dromedary has come up. If there's to be a third iteration of this > box: *Who will use it and for what?* > > I guess I'd start off thinking it's like the old one: used by > committers as a powerful place to do a lot of compiling and testing. > But is that right? If you are a committer and would (or would not!) use > it, please say so, and let me know what you'd be using it for. (What > else we might use a bunch of compute for is another question. This is > more about a box where you'd have a shell.) > > -- > rjbs I use dromedary. I use it for regenerating the Devel::PPPort data base, which requires lots of past perls. Tux keeps adding new development ones as they come out, and I filled in missing pieces, so that it has a complete set back to late 5.003. The box is slower than my own PC, now 2.5 years old. It is slower than the old dromedary as well. dromedary.p5h.org Linux 3.10.0-1127.13.1.el7.x86_64 [CentOS Linux 7.9.2009 (Core)] x86_64 Xeon(R) CPU E5-2650 v4 @ 2.20GHz/2200(4) x86_64 7982 Mb The old Dromedary had > 700 locales. This was invaluable for testing locale handling. That is missing from this. I would love to get those back. The old dromedary also had 24 cores. The old Dromedary had a windows VM hanging off it. I used it for debugging windows issues. I would love to get that back. In short, because of the deficiencies in the new Dromedary, I only use it for one thing, but would have other uses for it if they capabilities had been transferred over.Thread Previous