cherrytree

cherrytree copied to clipboard

CherryTree 0.99.46

Am wondering if this just me or maybe affecting everyone else using the program. I have always noticed when I first started using it, a slowdown in the program when accessing a node, or scrolling. I figured it would improve over a couple of version updates, but after three of them, it has not. So, I figure it might be something in the program itself, or maybe my notes is a lot? I have tried save/vac. My database is only 11M. Most content is just text.

Seeing if anyone else has experienced this before and maybe have ideas to try.

Thanks.

I work on Xubuntu 20.04 with quite large documents and everything works fine. The only lags I've experienced when saving files in sqlite format, so I save in xml.

I opened a new workbook and imported all content into it. Still slow. So, I guess maybe I have too many nodes/tabs. Maybe some are somehow only causing the problem and I need to recopy manually each one. Most of my nodes are plain text. Some are rich text, few have images. Hmmm.....

I saw a new version was posted, so I installed it. Started a fresh new workbook. Imported all my text (.txt) files. Still, crawls. Must be then how this laptop handles CherryTree.

And before anyone suggests I try another computer, I could but I can not. I am trying this program on my work laptop to keep my personal notes organized. I could put it on my home system, but since it is fifteen years aged and been jury-rigged as much as I could, I think it being slower than my VCR turning on be a bad indication of speed testing. Heck, my toaster can cook a waffle faster than it takes my home system to allow me to open a TXT file.

I think it is just related to the many tabs I have that are hundreds of lines long, some go into 2000s.

I also have a large CherryTree notebook, and have noticed lags. A side effect is that sometime it lags at a bad time while clicking on the node tree, and it can accidentally move a node (I raised #2483 for this problem).

I have noticed, at least for myself, that how bad the lags are is dependent on the number of nodes visited in the current session:

• If I've only visited a few nodes (even a few tens of nodes) CherryTree is quite fast and responsive
• If I've visited thousands (like would happen automatically when using "Find in Multiple Nodes") of nodes, that is when the program becomes slow and lagy. If I had to guess, all those nodes are still in memory. Once this happens, closing and restarting CherryTree makes it fast and responsive again (until the next time I use "Find in Multiple" again).