On Sat, 14 Oct 2006, Randal L. Schwartz wrote:
For the last "n" versions of DateTime::TimeZone (sorry, don't recall where it started), I've gotten a CPU-bound huge pause right after... ok 1545 - The object isa DateTime::TimeZone ok 1546 - name should be UTC ok 1547 - should not be floating ok 1548 - should be UTC ok 1549 - offset should be -18000 ok 1550 - name should be CDT ok 1551 - offset should be -21600 ok 1552 - name should be CST Takes about four minutes or so on my fast machine to get to test 1553. Is this expected? Is this just an OSX weirdness?
There's definitely something slow happening there. The test is checking that we can generate the DST changes for a given time zone up to the year 2200, which takes a non-trivial amount of time, and also will eat up a bit of memory, since changes are saved as they're generated.
On my machine, there's a pause there, but under a second. Four minutes is excessive, by that standard. OSX weirdness is a possibility. If it's a PPC chip, maybe that's part of the problem too. My machine's a 2.8ghz P4.
-dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
