starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 06:06:05 +03:00

[GH-ISSUE #2159] Floccus very slow on NC Bookmarks #1451

New issue

Open

opened 2026-02-25 22:40:03 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 22:40:03 +03:00

Owner

Originally created by @christianlupus on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2159

Which version of floccus are you using?

5.8.6

How many bookmarks do you have, roughly?

Are you using other means to sync bookmarks in parallel to floccus?

I had Firefox/Mozilla account active. It should be disabled AFAIK/understand.

Sync method

Nextcloud Bookmarks

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Firefox in various versions, e.g. 143.0.1

Which version of Nextcloud Bookmarks are you using? (if relevant)

16.0.1

Which version of Nextcloud? (if relevant)

32.0.2

What kind of WebDAV server are you using? (if relevant)

Nextcloud (same instance)

Describe the Bug

When using the NC bookmarks as backend, the sync of my bookmarks takes incredibly long. I was not able to sync the bookmarks within 10h or so. I let it run for that time and at some point it was aborted.

Using the same machine with the same folder to sync and either WebDAV or Git (using Gitea) takes in the range of 10sec for an initial sync. Any further sync might speed up to mere seconds.

Additionally, I do not get any kind of logs from floccus. Neither in the UI (sync settings). I opened the browser logs and did not see anything that seems to be related to Floccus. Thus, I need clear instructions on how to access valuable logs.

I have looked on the network activity and saw that the bookmarks seem to be processed in chunks (of 10 to 15 entries) that are individually sent to the server. Each (PUT) request takes ~10 to 20 sec to return. Thus, every 20 to 30 secs a new bunch is transmitted. This would mean approx. 3.5 hours of continuous communication.

Expected Behavior

All bookmarks get synced in reasonable time. Especially when running in regular intervals, sync should not take too long.

To Reproduce

Just have a bigger set of bookmarks on Firefox, install&configure the app and trigger sync.

Debug log provided

I have provided a debug log file

Originally created by @christianlupus on GitHub (Jan 30, 2026). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2159 ### Which version of floccus are you using? 5.8.6 ### How many bookmarks do you have, roughly? 5k ### Are you using other means to sync bookmarks in parallel to floccus? I had Firefox/Mozilla account active. It should be disabled AFAIK/understand. ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Firefox in various versions, e.g. 143.0.1 ### Which version of Nextcloud Bookmarks are you using? (if relevant) 16.0.1 ### Which version of Nextcloud? (if relevant) 32.0.2 ### What kind of WebDAV server are you using? (if relevant) Nextcloud (same instance) ### Describe the Bug When using the NC bookmarks as backend, the sync of my bookmarks takes incredibly long. I was not able to sync the bookmarks within 10h or so. I let it run for that time and at some point it was aborted. Using the same machine with the same folder to sync and either WebDAV or Git (using Gitea) takes in the range of 10sec for an initial sync. Any further sync might speed up to mere seconds. Additionally, I do not get any kind of logs from floccus. Neither in the UI (sync settings). I opened the browser logs and did not see anything that seems to be related to Floccus. Thus, I need clear instructions on how to access valuable logs. I have looked on the network activity and saw that the bookmarks seem to be processed in chunks (of 10 to 15 entries) that are individually sent to the server. Each (PUT) request takes ~10 to 20 sec to return. Thus, every 20 to 30 secs a new bunch is transmitted. This would mean approx. 3.5 hours of continuous communication. ### Expected Behavior All bookmarks get synced in reasonable time. Especially when running in regular intervals, sync should not take too long. ### To Reproduce Just have a bigger set of bookmarks on Firefox, install&configure the app and trigger sync. ### Debug log provided - [ ] I have provided a debug log file

kerem added the

bug

label

2026-02-25 22:40:03 +03:00

kerem commented

2026-02-25 22:40:03 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 30, 2026):

Hello! 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! 💙

@github-actions[bot] commented on GitHub (Jan 30, 2026): Hello! :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! :blue_heart:

kerem commented

2026-02-25 22:40:03 +03:00

Author

Owner

@marcelklehr commented on GitHub (Feb 1, 2026):

Hi @christianlupus
Thank you for reporting this!
Do you have APCu enabled? If not this would make a big difference. Other than that 5k bookmarks should be synced up quite quickly, from my tests with NC Bookmarks. Is your server machine on the low end spec wise, perhaps?
Also, when you reported this to me 1-1, v5.8.6 was not out yet, so perhaps you can retry with that version unless you're certain that you tried it with v5.8.6

@marcelklehr commented on GitHub (Feb 1, 2026): Hi @christianlupus Thank you for reporting this! Do you have APCu enabled? If not this would make a big difference. Other than that 5k bookmarks should be synced up quite quickly, from my tests with NC Bookmarks. Is your server machine on the low end spec wise, perhaps? Also, when you reported this to me 1-1, v5.8.6 was not out yet, so perhaps you can retry with that version unless you're certain that you tried it with v5.8.6

kerem commented

2026-02-25 22:40:03 +03:00

Author

Owner

@marcelklehr commented on GitHub (Feb 20, 2026):

Any update? :)

@marcelklehr commented on GitHub (Feb 20, 2026): Any update? :)

kerem commented

2026-02-25 22:40:03 +03:00

Author

Owner

@christianlupus commented on GitHub (Feb 20, 2026):

I am currently on vacation and on a business trip next week. Thus, I can only give you static information not a full test at the moment.

I do use the docker image called nextcloud. I think APCu is active there. At least it is listed as active module.
The server is a Intel Celeron machine with 32GB of RAM. I have to admit that the machine is under continuous load but still... Yeah, it is no Threadripper CPU or so.

I will retry on the latest version if I am back and updated to the latest bookmark (whatever this is at that time).

@christianlupus commented on GitHub (Feb 20, 2026): I am currently on vacation and on a business trip next week. Thus, I can only give you static information not a full test at the moment. I do use the docker image called `nextcloud`. I think APCu is active there. At least it is listed as active module. The server is a Intel Celeron machine with 32GB of RAM. I have to admit that the machine is under continuous load but still... Yeah, it is no Threadripper CPU or so. I will retry on the latest version if I am back and updated to the latest bookmark (whatever this is at that time).

kerem referenced this issue

2026-02-25 23:31:09 +03:00

[PR #1451] [MERGED] fix(XbelSerializer): titles need their own <title> element #1894

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#1451

No description provided.

Rows
Columns