On Apr 18, 2012, at 9:31 PM, Gil LB wrote: > Hello everybody, first, I am sorry about english mistakes, I am brasilian =) > > I have an application that have a huge data, but a small part of it is always > accessed all the time by all the users. > > I am thinking about having a cache in the application state, on an matrix, > but I am looking for some advice of you. > The data should be ordered by X and Y coordinates, and will be iterated > everytime some user want to know which data is near of him by the coordinates. > > Example: > > var data = [ > 31: [ > 56: "entry1", > 58: "entry2", > 78: "entry3" > ] > 34: [ > 2: "entry4" > ] > ]; > //it will be a lot larger than that > > //and the user will call something like: > findAllEntriesNear(32, 30); > > It is a good idea store in an Matrix like that? > > Thank you everybody =) > > Gil Lopes Bueno
Hi, Searching cached, in-memory data is always a good idea. If you want to make it even faster, or if it's growing too big, you can move it out of node's main thread to a thread_a_gogo running in parallel in the background, using the threads_a_gogo module: <https://github.com/xk/node-threads-a-gogo> -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
