floccus: Performance: Gets stuck at "Synching..." and never finishes

Just a quick update if anyone else is interessted in a solution for Android: the latest version of Kiwi-Browser supports Chrome extensions - not all are working but floccus is 😄

Hard to say from my perspective. Would surprise me if so, but can’t hurt to allow it. Essentially the problem some might face (and I do) is that they are running NextCloudPi so on a Raspberry Pi, which is not exactly a performance demon 😉, and it wouldn’t take much to go wrong in one with regard to memory consumption or leaks to bring it down to real slow rates, that a reboot might might fix.

On top of that it sites behind a domestic interrnet link which in Australia at least implies heavy asymmetry in speed, nominally I’m on a 50/20 Mbps link meaning 50Mpbs incoming and 20Mbps outgoing. Still, 20Mbps should be more than enough to satisfy a bookmark transfer within a minute, plenty more than enough, so if things got real slow it would be suggesting either congestion on the provider side that sees service level drop, or congestion on my side (as in I also run a few other things like a website or two on the same link 😉. though it’s hard to imagine anything I do congesting 20Mpbs. It’s easy to forget just how blazingly fast modern links are (given I grew up on 300bps links 😉 and we were running websites on 256 and 512 bps and the 1 Mbps links happily for some time.

Perhaps more important than a longer timeout (though the flexibility to exeperiment with one is never amiss) is if the floccus fails on a timeout there’s a clear indication either on screen or in the debug log as to what it was waiting on. Like had it got any response out of the remote server yet, a successful handshake, login, etc and is timing out on some later step or is it timing out on the initial contact effort.

The reason being these are very different scenarios to diagnose. One is connectivity full stop and the other is the response time of the bookmarks app on Nextcloud for expampel.

Anyhow, juts my idle thoughts. Mine seems to have finally synched again after weeks of hanging, and I’m really not sure what changed (or better said what change helped that along). The main change is that I upgraded my NexcloudPi server the whole schemozzle, every little bit of it that wanted an upgrade or told me it had one available, so that’s at the Respbian level, the NextCLoudPI level and the Nextcloud level and the Nextcloud Apps level … so it’s all totally satisfied happy chappy up to date on everything.

I’m not sure if anything else changed.

What was bugging me is that even the Cancel button on Floccus was not responding, and so browser restarts were involved as well, and there might have been a browser upgrade or two involved in that (as on the Linux side at least upgrades are so stunningly unintrusive and elegant it’s not funny, as in you just OK the upgrades notified but nothing ever, wants to be, asks to be, let along insists to be restarted - which Windoze always forces upon me! - and the update happens silently and without notice on next restart of the box, or app as relevant, so a restart of browsers on a Linxu box might well see updates applied).

So given all those updates it’s really hard to know what might have loosened things up again and seen successful synching! I will see at work tomorrow if my WIndoze browsers likewise respond with success.

v3.4.0 (currently in beta: #338 ) leverages a new endpoint of the bookmarks app, which dramatically reduces sync duration with nextcloud:

adapter	cold initial sync (4000 Bookmarks)	warm sync with no changes (4000 Bookmarks)
nextcloud-folders	~7min	~20s
webdav	~4min	~10s

This is the latest in a series of improvements that have reduced initial sync time from initially multipe hours to half an hour to now 7 minutes.

while working fine 2 days ago yesterday my server (4 cores, 6gb ram) got crushed by the the workload produced by floccus

I recently got an idea on how to further reduce the workload on cold-cache syncs, which will hopefully mitigate this kind of issue.

Do you have any suggestions?

I sadly don’t know of any xbel viewer apps.

The only downside of webdav is that you won’t be able to use the nextcloud bookmarks UI. Other than that, by all means try it! 😃

ah okay, I’ll stay on the nextcloud-version in this case sicne I didn’t find a decent way to use XBEL-files on Android. BUT: I’ve just set up my account from scratch and ticked the parallel-sync box which improves sync speed on chrome A LOT! Will have to check if this stays the same when I set up all other browsers/machines as well but currently this looks very promising - thanks again for this great extension! 😃

I have this same problem. I’m syncing to XBEL via WebDAV with NextCloud. Now, I have no less than 40,000 bookmarks - a big job for sure. However, it will spin for four or FIVE HOURS easily and never ever finish. It consistently leaves the .lock file in place and complains about it on each sync. This is probably because it never really finishes. I left it on all night last night doing a sync. It uses a massive amount of CPU time doing it, used up all my memory (16GB) and just about froze the system (memory leak?), and generally does not perform as advertised. Still, great concept and I’m looking forward to updates and bug fixes. I just need a simple bullet-proof solution that works with my NextCloud. One thing that might be nice is a progress bar on the sync to see where it is in the process.