#1
|
|||
|
|||
database periodic saves either too long or broken
It's been a long time I noticed this
but today I had an electric power shutdown in my region and it happened exactly at the right time (you will understand if you read the rest) so the situation : today I start up JD it has 3 download links left to download in a multipart archive those 3 links are respectively 700, 700 & 670 MB now I started JD & the downloads & did something else estimated download time: (700MB + 700MB + 670MB) / 1MB/s *60s = approximately 35 minutes now sometime this afternoon the powershutdown happened & therefore I had no time to quit JD. after a lot of hours, power is back on : I start back JD & JD thinks nothing was downloaded today, therefore it asks me whether to ignore the 3 files or redownload them. I ignore the 3, it then proceeds to extract the whole multipart archive successfully (and I'll add that the content was unaltered) conclusion : in at the very least 35 minutes no database save was done at all. All downloads were stopped at the end since nothing else was on the download list... therefore my theory is that database periodic saving is either : broken or too long. (or not enough triggers) which is the reason why I report this as a bug. PS: I'll add that maybe it's my computer however it's not the first computer where I notice a similar problem, it's just the first time that I have enough data on this. Last edited by Jiaz; 15.09.2011 at 09:56. |
#2
|
||||
|
||||
You can check the database.script's "date modified" at any time. Did you check it before restart JD? The problem is not the periodic saving but something else.
|
#3
|
|||
|
|||
no I didn't
sorry didn't know I had to look for it however I just had a save @4:16 the previous one was @3:36 however no downloads were running during that time so... the question is : what this "something else" can be in your opinion ? |
#4
|
||||
|
||||
I have just checked it myself, 15, 30, 30 minutes. Yours, 40 minutes. Not consistent, but it's exist. Despite of that, people still report problems. I have no clue.
Good news is, next major release will have different method. |
#5
|
|||
|
|||
@whismerhill
jD saves its database every 10 minutes. When your system is under stress it's possible the interval becomes larger, like 11 or 12 minutes. Also when you jD's queue is changed or when you change some setting the database is saved. When you're downloading files that can't be resumed (fileserve.com links for instance) then this save operation doesn't help in case of unexpected problems like power cuts. |
#6
|
||||
|
||||
the complete backend has been rewritten, please wait for next major update.
__________________
JD-Dev & Server-Admin |
Thread Tools | |
Display Modes | |
|
|