zim-wiki team mailing list archive

[hansbkk@xxxxxxxxx]

YES!

Setting it to "shared" - I also deleted the .zim structure and
re-indexed - makes things much snappier - I still see the python
processes hitting the CPU quite a bit, not quite pegging but close,
but the UI gives me the new pages when navigating, creating links etc
in a second or two.

Only tested for a few minutes so far, but so far so good.  . .

BTW just out of curiosity, where are the indexes now?


On Mon, May 12, 2014 at 8:54 AM, Jaap Karssenberg
<jaap.karssenberg@xxxxxxxxx> wrote:
>
> Hans,
>
> In general zim should not have issues handling a few thousand files - it is
> built rather scalable. However there may be some issue where the way zim
> accesses the drive conflicts with assumptions in encfs.
>
> One thing that comes to mind is to set the "shared" property - be aware:
> this will cache the index outside of the encfs folder. See if the index
> access is the bottleneck here.
>
> Otherwise we would need to think how to insert timers to figure out the
> exact piece of code that causes the delay.
>
> Regards,
>
> Jaap
>
>
>
>
> On Fri, May 9, 2014 at 5:11 PM, <hansbkk@xxxxxxxxx> wrote:
>>
>> files - 1100 including attachments (docroot), 860 just for the wiki
>>
>> folders - 280 total, 200 just for the wiki
>>
>> timedstats for *.txt
>> 16673 69699 590562 total
>>
>> real 0m0.439s
>> user 0m0.059s
>> sys 0m0.064s
>>
>> I don't do inline attachments or pasted images at all, everything not
>> *.txt is in the docroot tree
>>
>> I have no trouble at all accessing the tree with other tools, only in
>> Zim, in System Monitor or htop can see the Python processes spiking on
>> both processors to 100% while the graying out occurs.
>>
>> Shutting down everything python and then re-starting doesn't help,
>> symptom can occur right after a restart.
>>
>>
>> On Fri, May 9, 2014 at 10:50 AM, Sylvain Viart <launchpad@xxxxxxxxxxxx>
>> wrote:
>> > Hi Hans,
>> >
>> > I guess…
>> >
>> > Le 09/05/2014 16:03, hansbkk@xxxxxxxxx a écrit :
>> >
>> >> Just created a new notebook and WOW is that nice and snappy.
>> >>
>> >> Confirmed it wasn't the fact it was on an encfs filesystem, nor that
>> >> dropbox is sync'ing while things are unencrypted
>> >>
>> >> I guess I just let my "main" tree get too large?
>> >
>> >
>> > could you give use a idea of your notebook size?
>> >
>> > # all files:
>> > $ find ~/Notebooks/Notes/ | wc -l
>> > 404
>> > # folders:
>> > $ find ~/Notebooks/Notes/ -type d | wc -l
>> > 79
>> > # pasted images
>> > $ find ~/Notebooks/Notes/ -name pasted_image\* | wc -l
>> > 43
>> > # stats of all .txt files (lines words character)
>> > $ find ~/Notebooks/Notes/ -name \*.txt -print0 | wc --files0-from=- |
>> > grep
>> > 'total$'
>> > 12162 65938 523762 total
>> >
>> > You can prefix command with time:
>> >
>> > time find ~/Notebooks/Notes/ -name \*.txt -print0 | wc --files0-from=- |
>> > grep 'total$'
>> > 12162 65938 523762 total
>> >
>> > real    0m0.081s
>> > user    0m0.060s
>> > sys    0m0.024s
>> >
>> >
>> > Regards,
>> > Sylvain.
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~zim-wiki
>> > Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~zim-wiki
>> > More help   : https://help.launchpad.net/ListHelp
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp
>
>