Hi Jonathan. Thank You for the clarification, yes, I saw this is in the code. I'll try avoid map creation.
Best Regards. On Thu, Mar 4, 2010 at 12:21 AM, Jonathan Gray <[email protected]> wrote: > Just to reiterate and confirm what Erik is saying, building the Map will > internally iterate all of the KeyValues, dissect each one, and do lots of > insertions in the map. It will be less efficient than just iterating the > list of KVs directly yourself and pulling out only what you need from each. > > JG > > -----Original Message----- > From: Erik Holstad [mailto:[email protected]] > Sent: Wednesday, March 03, 2010 2:00 PM > To: [email protected] > Subject: Re: Timestamp of specific row and colmun > > Hey Slava! > I actually think that iterating the list is going to be faster since you > don't have to create > the map first, but that kinda depends on how you are planning to use the > data afterwards, > but please let me know if you get a different result. > The reason that there isn't a more "elegant" way of getting the timestamp > is > that we > wanted to make everything as bare bones as possible to improve speed. > Creating the map from the list on the client side and getting your > timestamps is still > going to be about 10-100x faster then with your old code, hopefully :) > > -- > Regards Erik > >
