I'm not sure what the "1800" tiddlers is based on. In my tests, all the 
tiddler titles loaded. Behind the scenes, apparently the server was stilll 
fishing for tiddler text. It must have been using an internal array to save 
results while waiting for (non-existent) data to load. The server crashed 
after the server had reported 1862 load attempts. But that's just as far as 
the reporting got. Internally, it may have had all the load events queued. 
The output reporting would have just lagged. So, I think,it would be more 
about machine processing maching. I'm running at 3.2 Ghz. I suspect solex's 
processing speed is similar.

The way I captured the report is to use the > operator to funnel the output 
of the node launch into a text file. Then I could look at the file and 
count how many load entries there were. solex could repeat the process with 
his own device. It would be a doubtful coincidence if our count was exactly 
the same. In that case, maybe there's a pre-set number of threads?


-- Mark

On Tuesday, June 4, 2019 at 7:51:40 AM UTC-7, @TiddlyTweeter wrote:
>
> Jeremy Ruston wrote:
>>
>> This isn’t actually a bug, it’s more of an unexpected consequence of the 
>> way that lazy loading is implemented: in client-server mode, if the browser 
>> references a skinny tiddler (one that lacks a text field) then it requests 
>> the body from the server. 
>>
>
> My impression reading the thread is that the "break-down" occurs at a 
> specific point?
>
> I mean, a server overload I can't see happening at a specific number on 
> different machines. That has to be code?
>
> I remain hazy whether this is able to be replicated at a set number? But 
> that was my naive first impression--that it does?
>
> Side thoughts
> Josiah
>
>  
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
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/74240656-125c-47c1-b2a0-e09efe6bf852%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to