Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tree operations become slow in very big files #269

Open
bakbuk opened this issue Jul 24, 2017 · 11 comments
Open

Tree operations become slow in very big files #269

bakbuk opened this issue Jul 24, 2017 · 11 comments

Comments

@bakbuk
Copy link

bakbuk commented Jul 24, 2017

I have a 15mb file with about 3000 rich text nodes in it. Two operations which were previously very fast had become slow: file save (1-2 seconds), and more crucially, adding a node in the tree (5-6 seconds). Is this sort of slowdown inevitable in such big files or perhaps some optimization is possible to speed things up?

I could provide such big file for testing if that'd be helpful.

@giuspen
Copy link
Owner

giuspen commented Jul 25, 2017

I'm in the process of porting to c++ / gtkmm3 as you can read in the forum, after that I'm sure the app will be way faster

@prog20901
Copy link

Thanks a lot and will keeping watching on the forthcoming fixes of gtkmm3..Have a nice day.

@prog20901
Copy link

Does it will create index and search through the index like Apache lucene or solr or elastic search ? Searching the contents every time will be a performance issue always until they is a mechanism to build the index and search through it like Acrobat DC creates index, Docfetcher creates index before performs the search.

@prog20901
Copy link

@giuspen Is porting to c++ / gtkmm3 has been done ? Do you have any updates on this issue?

@giuspen
Copy link
Owner

giuspen commented Jul 14, 2018

I'm still working on the porting but there is still a lot of work to do. There may be more minor pygtk2 releases before the first gtkmm3 version will be issued

@prog20901
Copy link

Is porting to c++ / gtkmm3 is done and the performancee has been fixed?

@giuspen
Copy link
Owner

giuspen commented Sep 8, 2018

It is ongoing in the subfolder "future" but still slowly, hope to speed up soon

@chamalis
Copy link

chamalis commented Apr 8, 2019

I think it's mostly proportional to the size of the database itself. The size of my database is 27MB and I need to wait 10-15 seconds to perform a save. My tree consists of:

  • 4 top-level nodes
  • Max-Depth: 3
  • total nodes: 100-130, rich text nodes with pictures (screenshots)

Porting to C++ will be a life-saver. Thank you for the app anyway. Its very useful!

@giuspen
Copy link
Owner

giuspen commented Apr 10, 2019

@chefarov for such large db you should use sqlite / ctb - that should not take so long to save

@chamalis
Copy link

@giuspen You are right of course. I can't believe I had missed that option at the time. Thanks.

@samuelkathiresan
Copy link

@giuspen is the porting has been completed in the new version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants