← Back to context

Comment by rubymamis

1 year ago

Anytype is extremely slow and a resource hog, similar to its other Electron counterparts, as can be seen on a benchmark I did.[1]

I’m developing Plume[1] which has a similar advanced block editor but since it’s built with Qt C++ and QML, is very performant (more so than comparable native apps!).

EDIT: Some work in progress: https://imgur.com/a/LwitrHe

[1] https://www.get-plume.com/

I wouldn't say it's extremely slow. While benchmarks can be useful, they often don't align with real-world experiences. What exactly are you comparing? Is it just rendering time? Have you considered a user's workflow, which might involve navigating through several pages or objects? In reality, we've attracted many users because they find 'Notion' to be slow, and many appreciate the speed of Anytype. Based on this, I believe it's not fair to give Anytype the same rating as Notion in your diagram. Also, I would assign a higher rating to Bear and Craft; their desktop apps are faster since they are native.

There is significant room for improvement, and we're already steps ahead in this area with our native mobile clients that sync peer-to-peer. Try our Android app and see for yourself. I hope that within the next three years, we'll excel with native desktop applications as well.

The value proposition of Plume looks good; I've left my email.

  • Hi! If you click on the "More details" button, you'll see the following table[1].

    Here's the methodology (also available on the website):

    1. Loading time: Fully loads the entire text and ready to scroll.

    2. Memory use after load: Memory used by the app after loading the text.

    3. Scroll jump: How fast the app scrolls when dragging the scrollbar to a far position.

    4. Resize: How fast the app resizes after scrolling to the middle of the text.

    5. Select all: How fast the app is at multiple operations: Select all text, cut, paste, undo, redo.

    6. Editing: How fast the app is at typing at the middle of the text?

    7. Memory use second time: Memory usage after doing all the above operations multiple times.

    8. Binary size: Binary size of the app.

    9. Cross-platform: Can the app run on Windows, Linux and macOS?

    I think these are very fair benchmarks. And objectively speaking, both Bear and Craft didn't perform well (well, Craft couldn't load the text since it has a limit on the amount of paragraphs it can load).

    EDIT: Just noticed you signed up! Thanks for that! BTW, I did try Anytype's iOS app and it was very smooth compared to the web/Electron one.

    [1] https://imgur.com/vEfV7Iq

    • Huh - it was surprising how poorly Bear fares in that benchmark given I use it regularly and find it snappy and responsive. But then I looked closer and saw you were loading War and Peace into it.

      I'll let you in on a dirty secret: Most of my documents aren't as long as war and peace. I care a lot more about "normal" document sizes and real world typing latency. Is Anytype actually slow in this case?

      3 replies →

What sets Anytype apart as a local player is its notion-style databases, and I believe it is unique in that respect.

If the outlining experience is good enough (drag/drop, collapse...), I will definitely try Plume for "light/fast" note-taking.

  • I've decided to depart from the complexity of databases. Instead, Plume is going to be more opinionated and simple. It will support Kanban boards, tables, columns, images and other complex block types, but the data won't be separated into different "databases". Essentially, each note in Plume is a simple markdown/plaintext file.

    Drag and drop and collapsible blocks will be supported for sure, so sign up for the wait list and check it out upon its release (: