Running 5481 on file with large nodes. set g.cache_color_info to True; removed @killcolor, first impression large nodes switching seems sluggish as ever. But oh wait! There is significant improvement if I come back to a node that was previously selected. Of course! At first time selection the cache is still cold!
The memory usage increase seems fairly benign for today's computers. For large nodes the speedup is quite significant. Could this feature be turned on as a directive like @killcolor. So we can just @cachecolor to enable color caching at a large node (and its children). Another observation: With caching turned on, if I @killcolor a node, the sub nodes that were visited already maintain their cached colors while the unvisited nodes don't have color. Interesting interaction of features here. On Wednesday, October 3, 2012 7:01:31 AM UTC-7, Edward K. Ream wrote: > > On Wednesday, October 3, 2012 8:49:57 AM UTC-5, Edward K. Ream wrote: > > > Color caching speeds up coloring of previously-colored nodes by about a > factor of 5. > > Better measurements indicate that cached coloring is a little less than > twice as fast as uncached coloring for large nodes. This isn't a trivial, > but it is not as much as I had hoped. I'm not sure the speedup is > worthwhile. Please let me know what you think. > > Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/FUS3OnYy65QJ. 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/leo-editor?hl=en.
