etesync-server

Commit Graph

Author	SHA1	Message	Date
Tom Hacohen	a54afd5210	Optimize stoken-using functions to only account for current revisions. No need to account for revisions that are not current when calculating stokens because those, by definition, are not the latest ones, and therefore won't have the most recent stokens. This becomes a problem when collections have many associated revisions.	9 months ago
Tom Hacohen	2f1f95fea9	Optimize how we fetch the latest (current) revision The way were were doing it was implicitly sorting the query items and it was causing millions of items to be sorted (even though the result should only have one) making it slow. By switching away from `get()` and `first()` we are telling django to not try to sort.	2 years ago
Xiretza	ada5181a7e	fix: move django_etebase module from toplevel to under etebase_server This is in preparation for creating a python package, which should only occupy the "etebase_server" name in the global module namespace.	2 years ago

Author

SHA1

Message

Date

Tom Hacohen

a54afd5210

Optimize stoken-using functions to only account for current revisions.

No need to account for revisions that are not current when calculating stokens
because those, by definition, are not the latest ones, and therefore won't have
the most recent stokens.

This becomes a problem when collections have many associated revisions.

Tom Hacohen

2f1f95fea9

Optimize how we fetch the latest (current) revision

The way were were doing it was implicitly sorting the query items and it
was causing millions of items to be sorted (even though the result should
only have one) making it slow.

By switching away from `get()` and `first()` we are telling django to
not try to sort.

Xiretza

ada5181a7e

fix: move django_etebase module from toplevel to under etebase_server

This is in preparation for creating a python package, which should only
occupy the "etebase_server" name in the global module namespace.

3 Commits (master)