85% faster LDAP, 10x read/write speed of Windows Network Drive: Welcome to Nextcloud 13 Beta

Originally published at: https://nextcloud.com/blog/85-faster-ldap-10x-readwrite-speed-of-windows-network-drive-welcome-to-nextcloud-13-beta/

We know, it is crazy, this is just the beta. You’ve already seen us publish a draft of our End-to-end Encryption feature coming to Nextcloud 13 and here is another peek into what is coming: SPEED. Boatloads.

Remember Nextcloud 11? This release resulted in the TU Berlin cutting their database load in half upon migration and while this performance advantage is yet unmatched, the upcoming 13 is slated to introduce its own slew of improvements. The story starts with LDAP returning user information over 85% faster in a torturous test we devised; and continues with improvements to our external storage capabilities giving system administrators employing php-smbclient for their Windows Network Drive a 10x speedup in sequential read/write to look forward to. There is more and we encourage you to read on but, perhaps most importantly, download the beta and give it some in depth testing! Open Source software is only as good as its numerous contributors and no test matrix can replicate what you lot throw at our software every single day. Testing Nextcloud 13 Beta 1 against your unique requirements is what will ensure its ultimate stability and usability, so give it a good run!

First awesomeness: LDAP

For Nextcloud 13, we'll introduce a small but very nice feature: auto-complete of user names in the comments field. Here's a video for you to enjoy the results, made by Arthur, its principal author.

For this feature to work well, it is important to get a list of matching users to the browser as quickly as possible. On enterprise installations, this typically means going through the LDAP code in Nextcloud, ultimately checking with the LDAP server what users match the name you’re typing. You can probably imagine that with 150.000 users, this isn’t as snappy as on your home server with 5 users!

Consequently, this area needed work. A torture test was devised: setup a server with 150.000 users and ask it for users 1001 to 1500 that match the characters “ha”. This took a whole 15.2 seconds before the work started, making auto-complete in the share or comments dialogs less than fun. However, after the work was done, reviewed and merged, this same action took no more than 1.8 seconds! This will only work if the users have been fetched before at least once but on a running, busy, active server, the impact of this change should be noticeable very quickly.

Stay tuned for a post about the work on this by Arthur on his blog!

Besides some small improvements (like the addition of a save button for LDAP user credentials to avoid issues with browser auto-complete), another major change was integrated: a plugin mechanism which allows users to extend the Nextcloud LDAP features. Normally, Nextcloud does not require an LDAP server to give it write access, something security-conscious administrators appreciate. But sometimes it would just be darn useful to manage LDAP users from within Nextcloud and with this plugin structure, this would now be possible. An application to do some of this work was developed by the contributor of this code and while it is specific for a certain LDAP structure its code can certainly serve as an example for others.

Storage, Encryption and more

Our external storage code has seen optimizations as well. The load on the database was reduced for all external storage folders and as mentioned before, systems using php-smbclient to provide access to a Windows Network Drive or Samba share will see an improved sequential read/write speed of up to 10x! S3 external storage reduced its CPU load by 50% and its execution time by 73% (that means "it is almost 4x as fast with small files"), in addition to adding the ability to handle large files. It was previously limited to files about 5GB in size.

Our Server-side Encryption has been sped up as well, at least on new installations. Until now, per-user keys were used by default and administrators could enable the master key. This is now enabled by default, resulting in a significant speedup, while also working better when users are provisioned over LDAP and change their passwords. The change helps especially with large folders and makes group sharing instant. Login resets also work faster and easier. We recommend administrators to switch from per-user to master key encryption when enabling encryption to benefit from this performance improvement as well. Unfortunately existing installations can not switch over without disabling encryption, decrypting files, and re-enabling encryption.

There is more: search was improved, especially for large searches on large servers, reducing database load and runtime. The Contacts app loads large numbers of contacts much faster and deferred script loading in the browser was shown to decrease time it takes for the first page loading our files app by more than 50%!

End-to-end Encryption and more

We have continued to work on our new End-to-end Encryption feature and like last time ask for your feedback and input on this feature. More improvements are of course included in or coming with Nextcloud 13 but we don't want to spoil it all: go download it and see for yourself!
get Nextcloud 13 Beta NOW!


This release was developed by the wonderful Nextcloud community and we'd like to thank every single person involved for their help in making this happen! If you'd like to be part of the team that makes the best, most awesome private cloud technology in the world, join us!

SMB access using Nextcloud is indeed slow, sometimes the first load shows external storage mount points in red and an error that not all of them could be connected.

Improvements are highly appreciated, eager to test Nextcloud 13 now!


I’ve extend the config.php with the S3 part from my production system and this version ignored this part. All files are landed under the /data filesystem and not as expected at the S3 storage.

One positive: the web gui response is very fast.


1 Like

Sorry, my fault. I’ve forgotten a line.

Everything is working fine.


1 Like

You mean the master recovery key is enabled by default? Isn’t it more unsecure as the previous solution on user-key basis?


I’m not on the pulse of development. With which apps is the new end to end encryption possible at the moment?
I think I have read of android but how far is the linux desktop client?


It is pretty solid so far. With the integration of Exchange/IMAP in Mail, it is much more useful. We have Exchange, and having a decent Mail client on Linux is just what I wanted and needed.


I believe iOS is testing with Android right now, I’m not sure about the Desktop client status tbh

I’ve added beta 13 to the list of demo servers :wink:


@jospoortvliet I don’t see this version in the beta-release channel… https://nextcloud.com/release-channels/

with this beta,
theres no option to connect google drive anymore?
Please guide if it was removed or is temporary unavailable in beta?

It was removed:

So there will be no Dropbox or Google drive support anymore until someone makes an app/puts it into the app store.

1 Like

Can we have announcements/news be locked to mods and up only? These NEWS
threads are getting pretty chatty.

in beta,
my external storages dont work,
it shows under file but i cant open them.

ANY suggestions about this??

Why? Its great to discuss news items … important for me.

@clickwir Well, a forum is for discussion actually and these post are crossposted here exactly for that. If you want to view these posts without comments, go to https://nextcloud.com/blog. You can find that link on the top of every news piece.

I don’t see an update to nextcloud 13 for the beta channel on my nextcloud instance, only for version 12.0.4RC1. Is this on purpose or am I missing something?

1 Like

Was it me?
You replied for?

Dear Emi
You need to download it and upgrade nextcloud manually.

I like the combined user and admin settings @jospoortvliet & co, but I think the Personal and Administration headings should be more pronounced.