Le 11/12/2013 15:44, Sebastian Sastre a écrit :
Hi Thierry
On Dec 11, 2013, at 12:43 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote:
I have packages (in the order of hundreds of classes) and save delays and package click delays are starting to demand patience in a way that doesn't feel like the right path
Which operations ? I didn't remember noticing much with 179 classes on a laptop without a SSD.
choose one. Just for clicking the package that will should you UUID, version and author I need to wait ~16 seconds. Sounds like a lot of overhead for reading a small .json file.
This operation is fast with gitfiletree because I cache the commit history and avoid reading the version file everytime: the version reader is very slow, especially with large version files. You're using FileTree and not gitfiletree ? gitfiletree may solve the reading problem, if it fits with your workflow (and it reads cleanly pre-existing git/filetree repository without changing them).
But the write is the most worrisome
This is something I haven't found a need to optimise yet, so maybe you're on something important.
All that is with a SSD disk, otherwise save delays would be /way/ beyond unacceptable
I'd like to know more, and understand the reason, for sure. As far as I know, filetree will rewrite the whole package to disk everytime... and maybe optimising that could be the solution.
Well, that explains a lot. Writing all every time is the lazy thing that's okay for a prototype and temporary code in a proof of concept but that massive redundant reads certainly doesn't sounds like pro software. Specially for SSD's which has a limited quantity of writes
Well, it ensures correctness and simplify the code ;) When it is confirmed to be a bottleneck, then we can act and change it. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95