On Mon, 15 May 2006, Praveen Ray wrote:
If you have to create lots of objects from _different_ epochs, it's
probably going as fast as it can. However, if you're likely to see the same
epoch repeatedly, you could do some sort of memoization and see a speed
boost.
An XS backend to DateTime
If you have to create lots of objects from _different_ epochs, it's
probably going as fast as it can. However, if you're likely to see the
same epoch repeatedly, you could do some sort of memoization and see a
speed boost.
-dave
An XS backend to DateTime would also make it faster, won't
On Sat, 13 May 2006, Rick Measham wrote:
Lenny Rachitsky wrote:
I'm trying to improve the performance of some code, and I've found that a
lot of the inefficiencies I have are caused by a large number of DateTime
object creations.
Do you use every one of these DateTime objects, or are you just
Lenny Rachitsky wrote:
I'm trying to improve the performance of some code, and I've found that a
lot of the inefficiencies I have are caused by a large number of DateTime
object creations.
Do you use every one of these DateTime objects, or are you just creating
them all and only using some? If
On Fri, 12 May 2006, Lenny Rachitsky wrote:
I'm trying to improve the performance of some code, and I've found that
a lot of the inefficiencies I have are caused by a large number of
DateTime object creations. I would like to update the code to create the
object only once, and update it with d
I'm trying to improve the performance of some code, and I've found that a
lot of the inefficiencies I have are caused by a large number of DateTime
object creations. I would like to update the code to create the object only
once, and update it with different epoch times, instead of creating a new
