Replies: 27 comments 16 replies
-
Can you upload the database here? There are several explanations. First, BQ has to create 7106 * N display items. It then has to populate each of those items. Second, the Books query includes sub-queries for computing sums whereas your queries do not. |
Beta Was this translation helpful? Give feedback.
-
Also, Qt drivers do not necessarily support the size of a query's result set. I believe for PQ that they do and not for SQLite. As a result, each row of the table has to be added for a particular record. Setting the row count once is better. Some of the queries in BQ have corresponding count queries; this varies with the complexity of a query. |
Beta Was this translation helpful? Give feedback.
-
if all is normal it's great it was just an observation |
Beta Was this translation helpful? Give feedback.
-
I see. Yes, it lacks performance. |
Beta Was this translation helpful? Give feedback.
-
BQ spends 86 milliseconds on the query. As suspected, it's the 7106 * N items. |
Beta Was this translation helpful? Give feedback.
-
BQ also has to create the other view because the person way wish to see a graphical view of the contents. See View -> Icons Mode. |
Beta Was this translation helpful? Give feedback.
-
So it is creating two views. |
Beta Was this translation helpful? Give feedback.
-
Sure. If you change views, it would have to perform the query again. It does not have to if it caches the entire result. It has the cache in the table view but not in the icon view. |
Beta Was this translation helpful? Give feedback.
-
It creates default images. |
Beta Was this translation helpful? Give feedback.
-
BQ prefers pagination. The unlimited size was again a request. Users. |
Beta Was this translation helpful? Give feedback.
-
https://textbrowser.github.io/biblioteq/ May 15, 2011. |
Beta Was this translation helpful? Give feedback.
-
we all have our own way of working and the table view for me allows to make a classification and to detect the errors and correct them. practical exercise I put the table in unlimited, I classify by author and I see the 7 documents that I must modify. |
Beta Was this translation helpful? Give feedback.
-
this mode is made for the detection of the typing errors (with the resumption of the existing and it is very well like that) it will change the habits :-) but the people use the table view only when it meets a problem of shower / accession_number not valid. With BiblioteQ, there will be no more problem so the table view will be a bonus :-) |
Beta Was this translation helpful? Give feedback.
-
9176 ms for populating the table. |
Beta Was this translation helpful? Give feedback.
-
8328 without tool tips. |
Beta Was this translation helpful? Give feedback.
-
7597 without special ISBN formatting. |
Beta Was this translation helpful? Give feedback.
-
it's great it gives a perf table according to the requested options |
Beta Was this translation helpful? Give feedback.
-
Between 8 and 13 seconds. |
Beta Was this translation helpful? Give feedback.
-
7.5 (icons and table) without book-read status. |
Beta Was this translation helpful? Give feedback.
-
Cannot disable book-read status. |
Beta Was this translation helpful? Give feedback.
-
Another user request; the book-read status. |
Beta Was this translation helpful? Give feedback.
-
I'll add a new option to disable the icons if desired; with a nice warning. |
Beta Was this translation helpful? Give feedback.
-
100 items in about 212 ms. |
Beta Was this translation helpful? Give feedback.
-
Lots of new optimizations! :) New option for disabling the Read Status column along with a tool tip. See Other Options. |
Beta Was this translation helpful? Give feedback.
-
5.3 seconds. |
Beta Was this translation helpful? Give feedback.
-
With intelligent image caching. 1.5 seconds. |
Beta Was this translation helpful? Give feedback.
-
38466 saturn ./BiblioteQ 0 131.3M 140.9M 204.9M First entry reflects image caching. BQ consuming 131.3 MiB. Image caching is not a complete solution because unique images will require individual resources. |
Beta Was this translation helpful? Give feedback.
-
I start to use BiblioteQ in real condition : report on display speed
configuration :
Show Progress Dialogs disabled
Show Table / View Image disabled
Entrie per Page / Unlimited Entries per Page
Result:
by menu View/Category/Books : about 12 seconds to display my 7106 documents on 24 columns (with availability and totalreserved)
by sql about 3 seconds : "SELECT book_read,title,author,publisher,pdate,place,edition,category,language,id,price,monetary_units,quantity,binding_type,location,isbn13,lccontrolnumber,callnumber,deweynumber,originality,condition,accession_number FROM book"
availability,totalreserved" is missing, I didn't find it in the sql tables to have the 24 columns of the Books view
by sql about 6 seconds for "SELECT * FROM book" on 30 columns
I do not understand that we arrive at a factor of 4 between display by sql and the menu to display 2 more fields
can you look at this point, thank you for the time spent at BiblioteQ
Beta Was this translation helpful? Give feedback.
All reactions