I'm beginning a study on 1 Corinthians, so am creating a clippings document of outlines from the commentaries. But adding each outline takes around 15 seconds, during which time I can do nothing but wait. There's nothing unusual in the logs.
If Clippings is anything like Notes, maybe its a single XML entry in a single field of the database in question. If so, it needs to update and rewrite the entire thing for every edit you make.
From what I have seen, Notes does not scale for the ways some are using them. Maybe true of Clippings and other types too.
Logos4 seems to want to commit any edit to the database(s) and SYNC to Cloud after every tiny edit or so, unlike a tool like Word which sits quiet until you click Save (or Auto-save fires).
Bob has said he does not want to write a word-processor. It seems Notes (and related) is the wrong tool for a major study such as pulling all the various content and notes you want for all of 1 Cor.
Consider Word, or OneNote or any of the other 10s or 100s of such tools, and leave the internal Notes and Clippings for lesser works, with just a few minor reminders, paragraphs or whatever.
For me, I've decided to not really use Logos4 for user-content except very minor things, where I dont care about lossing it, or having a Beta trash it. Sad really. L3 was way better in these regards.
Yes, while Logos is using SQLite, rather than something like eXist, user documents are in XML - at least those I've explored in a SQLite browser. However, the only place I've seen this to cause a performance hit is in the Prayer Lists where the entire list is a single, sorted XML document.
I have pushed the envelope to discover that there is a maximum size (since modified) and stored multiple, very long entries in a single file. I get a performance hit when a long note is dense in Biblical references that are automatically linked. My first thought on what is causing the performance hit you are experiencing is the outline format which is not supported in Logos 4. I suspect that the format conversion code needs to be optimized.
Note: recently Bob P. said on the forums that Logos 4 specifically addressed the scaling problems of L3 and expects single large Note files rather than many smaller files.
It seems Notes (and related) is the wrong tool for a major study such as pulling all the various content and notes you want for all of 1 Cor.
This does not correspond with my experience.
As JimT knows from other threads, I strongly disagree on this. The advantages of the Logos searches of user data and the internal linkages means that using external note taking defeats a significant portion of the power of Logos 4. The performance issues of Notes and Clippings have been minimized for most users. However, there are users still experiencing serious problems which Logos has to identify and correct. And, yes, there are still a few functions that should be, but are not yet, available.
But adding each outline takes around 15 seconds
seems rather excessive..
Notes does not scale for the ways some are using them
each individual note is a seperate record in the database - notes are scalable on a megasize, I have to side with Bob on this one..
Maybe true of Clippings and other types too
clippings - as you say - are stored in a single record per whole clipping document, so yes in time there will be a slowdown while the content is exchanged/reindexed/synced, however, but Marks 15 secs seems a tad excessive.. despite there being more data to write to database for a clipping record. If the clipping is on a bible reference it also adds records to other tables (presumably so it shows in the user content), consequently theres more data to write when making a clipping than another type of document.
I've decided to not really use Logos4 for user-content except very minor things, where I dont care about lossing it, or having a Beta trash it.
I've checked, and each clipping file is a separate entry in the database. It would make more sense if each clipping was a separate entry - both for the sake of speed and to aid collision detection.
As a consequence, my clipping record takes up just over 450kb - which is somewhat on the large side, but still should be writeable in a few milliseconds. The logs and my user experience suggest that perhaps Logos is not syncing in the background.
Pictures are ignored cos v3 didnt have them either
Sorry, but I had whole files of pictures in V3 ... they didn't exactly convert over. [:D]
It would make more sense if each clipping was a separate entry
Not only for performance reasons but for maximum reuse of code. I can understand this on a prototype but not in production. The same flaw with the same performance hit occurs in Prayer Lists where I can perhaps exceed your 15 second problem.
Pictures are ignored cos v3 didnt have them either Sorry, but I had whole files of pictures in V3 ... they didn't exactly convert over.
Sorry, but I had whole files of pictures in V3 ... they didn't exactly convert over.
wheres the jealous symbol, I havent been able to embed pictures since v2.1
Sorry I presumed it was Logos3 rather than me cos i did ask..
I stand corrected..
It would make more sense if each clipping was a separate entry Not only for performance reasons but for maximum reuse of code. I can understand this on a prototype but not in production. The same flaw with the same performance hit occurs in Prayer Lists where I can perhaps exceed your 15 second problem.
Yes Absolutely, but you are preaching to the converted.. we can but hope this being remedied in a future release..
I just did a test and mine is lightning fast...I wonder if it makes a difference how many clippings and clipping files you have?
I don't have many at all...
I just did a test and mine is lightning fast...I wonder if it makes a difference how many clippings and clipping files you have? I don't have many at all...
In my experience, add about 30-50 in and you will begin to notice a slowdown..
I've submitted your report.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
