The graph itself is not massive (5000-10000 objects). But takes 10 seconds to traverse/update in some cases.
Probably I can multithread it. Just need to make sure DB is not in an exclusive lock :) Or even offloading it into queue may do the job. What do you think about it? On Nov 28, 2011 6:53 PM, "Nicholas Faiz" <[email protected]> wrote: > OOC, have you tried doing it with a regular traversal in, say, Ruby code? > Did it take very long? If you can multi-thread the tree structures it might > not be that big a problem? > > If it's a truly massive graph then you'd probably want something other > than SQL (as stated above). > > Cheers, > Nick > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rails-oceania/-/FqGMliNa4I4J. > 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/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
