[TW5] Search lag

[Jon]

Hi,

I use OneNote at work and find the search facility to be instantaneous i.e. results appear as you type.

At home, I'm using a reasonably quick laptop but when using the search box (and also editing) I find there is always a lag with TW and wondered whether it was technically possible for it to be as fast as OneNote?

Jon

[Mark S.]

How big is your TW? There is no real indexing in TW, so the larger the file, the slower it's going to be.

On a desktop computer, searches in  my 5Mb TW are nearly instantaneous. I also use an older tablet to search Bible (6 Mb) references. The slowness is noticeable, but acceptable.

The main thing  you can do is make sure that the "recent" tab isn't opened. Every key stroke will refresh the entire list, slowing things down. Switch to the "open" tab or some other tab. On mine, I've shortened the recent list, so even if it is open only a handful of entries show.

HTH
Mark

[Jon]

Hi Mark,

My TW is 9Mb. Search is still slow with the recent tab closed but I'll try it on the desktop at work to see how much of the lag is due to the computer.

Jon

[Mark S.]

10 Mb or so is where I expect to hit the wall, though others are more tolerant or have much more powerful computers.

What do you have in your TW that's racking it up to 10 Mb? If you have images, the best thing to do is to export them to external files in a subdirectory. I look at the TW/directory system as being the complete information system.

HTH
Mark

[Jon]

Hi Mark,

most of the images are in an external directory - it must be the lack of indexing that's the issue (and presumably OneNote has that)

Jon

[Josiah]

Ciao Jon

Its worth mentioning some factors involved ...

• as you mention, power of computer
• size of file (but see below)
• the browser you are using and its configuration

FYI over time there have been several tests of "capacity" of TW and its performance is not as simple as a function of file size alone.

In my own case I use one browser instance for TiddlyWiki and searches are faster than my other Firefox with dozens of open tabs.

best wishes

Josiah

[Tobias Beer]

Hi Jon,

Afaik, there is a "refresh" delay for each keypress only after which TiddlyWiki goes to fetch results.

If there isn't such a delay, then this needs to be implemented immediately.

There's this ticket, but I'm almost certain it is more or less unresolved:

refresh delay for text input fields
https://github.com/Jermolene/TiddlyWiki5/issues/1494

Anyway, are you slow typing your search keywords,
or rather: are you able to type fast enough w/o TiddlyWiki
busily hasting into a search for "a"?

I find it an impossibility that TiddlyWiki would do a search on a single letter,
For me, there needs to be an ability to say:
no search for less than x letters.

Best wishes,

Tobias.

[Jeremy Ruston]

Hi Tobias

Afaik, there is a "refresh" delay for each keypress only after which TiddlyWiki goes to fetch results.

The refresh delay only applies to modifications made to draft tiddlers, and so it doesn’t apply when typing in the search field.

If there isn't such a delay, then this needs to be implemented immediately.

There’s no restriction on the number of characters typed before a search is triggered.  I agree it would be a worthwhile enhancement.

There's this ticket, but I'm almost certain it is more or less unresolved:

Not exactly unresolved! There’s a specific proposal in the ticket, and I’ve repeatedly pointed out why I don’t believe that the proposal is viable.

Best wishes

Jeremy

refresh delay for text input fields
https://github.com/Jermolene/TiddlyWiki5/issues/1494

Anyway, are you slow typing your search keywords,
or rather: are you able to type fast enough w/o TiddlyWiki
busily hasting into a search for "a"?

I find it an impossibility that TiddlyWiki would do a search on a single letter,
For me, there needs to be an ability to say:
no search for less than x letters.

Best wishes,

Tobias.

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a49e9f73-0899-4ec4-9561-3837071f5779%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jon]

Thanks for the replies - yes, I've definitely found that closing other browser tabs makes a big difference, so as suggested, I've got the TW open in a single tab in Firefox whilst Chrome is open for other stuff.

Jon

[Jeremy Ruston]

I’ve pushed a fix to add a minimum length threshold for the search field:

https://github.com/Jermolene/TiddlyWiki5/issues/2603

New minlength operator committed in:

https://github.com/Jermolene/TiddlyWiki5/commit/ffcbcbfa82cb8f1044c57967117aeae0978579f0

Search length threshold committed in:

https://github.com/Jermolene/TiddlyWiki5/commit/989cee50594a76a0f30d1d2124ce9e5e5808c6cf

I’ve also uploaded a prerelease for you to try:

http://tiddlywiki.com/prerelease

Best wishes

Jeremy

-- 
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9561b9af-7c42-427c-a452-d6116f965352%40googlegroups.com.

[Jon]

That does seem faster, Jeremy.

Many thanks

Jon

[Riz]

Is there a workaround to perform the search only when pressing the enter key or something.  Also, will there be a similar solution for the slow edit text fields? A work around will do too

[Mark S.]

Will we be able to effectively turn this feature off by putting it something like 100? Especially on a device, with a software keyboard, typing a wrong character becomes overly expensive. I'd much rather check my work and have the search begin after the phrase is right.

Thanks!
Mark

[Jeremy Ruston]

Hi Mark

Will we be able to effectively turn this feature off by putting it something like 100? Especially on a device, with a software keyboard, typing a wrong character becomes overly expensive. I'd much rather check my work and have the search begin after the phrase is right.

By “turning this feature off” presumably you don’t mean revert to the previous behaviour, but rather you want to trigger the search manually, by pressing enter, or something. The change I have made does not introduce that new behaviour.

Best wishes

Jeremy.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/84a66e51-058e-49fa-861f-9d2fd1afe978%40googlegroups.com.

[Jeremy Ruston]

Hi Riz

Is there a workaround to perform the search only when pressing the enter key or something.

No, not at present. But there’s nothing to stop anybody building an alternative search implementation that requires “enter” to trigger the search.

Also, will there be a similar solution for the slow edit text fields? A work around will do too

I don’t think there’s a similar solution for slow edit text fields. At least, not one expressed in terms of changing behaviour depending upon the number of characters typed.

Best wishes

Jeremy.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7a463af5-72ab-4e9f-8469-9c61bd182ad3%40googlegroups.com.