Yes, I’ve experienced this (in older Pharo versions mind you). We explicitly don’t use DateAndTime / Date / Timestamp in such cases but store an integer representation instead. We can always reify that if we need to and still have good comparison speeds.
Cheers, Max On 26.03.2014, at 22:21, Esteban A. Maringolo <[email protected]> wrote: > I'm grouping by date a resultset coming from the database, it > cointains around 2000 dated objects. > > It is: > myObject groupBy: #date. > > But turn's out that DateAndTime #= comparison is elegant object-wise > but not performance-wise. Because it instantiates several other > objects along the way. > > This is in the milliseconds range, but in the agregate of a couple of > thousand of objects, it creates a lot of not-simple-objects (it is, > not integers), and maybe because of that it isn't as fast as I'd > expect. > > Did somebody experienced this too? > > Regards, > > Esteban A. Maringolo >
