I've encountered 2 problems using cqrlog on Ubuntu 13.04 after upgrade to 1.6.0.
1. Every now and then I'm prompted to import new QSL manager database and DXCC table, but importing them takes ages (ca. 25min) and during that time there's a massive disk usage.
2. I see 2x cqrlog icon in Unity launcher when I open a database.
Did anyone see this, too?
Marek SQ3HTX
Both QSL managers (zip, 240 kB) and country files (tar.gz, 740 kB) are of minimal size. No reason to import such files in 25 minutes. Also Unity launcher displays only one icon. Using Ubuntu 12.04 LTS.
The most time consumpting procedure is the import of QSL managers. The unpacked files has 690 kB and contains 33066 QSL routes. My ancient machine (2 GHz, 2 GB RAM) needs ~ 8 seconds to import this. The import of country files takes ~ 1 second.
I recommend to inspect your system. Some rumours says that the 13.04 is much worse than the 12.04 LTS. Consider a downgrade!
Martin, my Mint 13 LTS takes a lot longer as well, still the same OS version as with the previous version of CQRlog, import takes a very long time, as does EQSL and LOTW downloads, I don't think I have yet completed a download cycle yet of Managers etc, It takes soooo long I just hit the (x) then the OS asks me to force quit because the program is no longer responding. might just down grade back to the previous version of CQRlog.
Tom K8WDX
I doubt it's the system itself, previous version of cqrlog worked fine. I debug mode I can see sql updates one per qsl manager entry and they are executed rather slowly. Maybe it's mysql, I'll try to look into the logs. Problem with launcher disappeared after unity reset.
Opps forgot to mention,
4X AMD Athlon(tm) II X4 630 Processor 12 gigs of ram
Tom K8WDX
Weird. I experience none of those problems in Mint 14. I do, however, have the MySql bug. Most of the time, not always, MySql seems to have stopped after a while of not touching CQRlog. Intel Core I7 920 with 6 GB RAM.
I see the slow database behavior. It is slow if you choose to save data on the local machine, and much worse if you choose not to save the data locally, and use the regular MySQL server (even on localhost).
Updating QSL managers takes 5-6 minutes, and updating the 10-10 membership list takes a very long time. (So far I've not allowed it to complete, but it has run about 30 minutes without completing.)
While this is happening, I can hear the disk churning and iostat says that my cpu use is:
avg-cpu: %user %nice %system %iowait %steal %idle
0.71 0.00 0.50 23.68 0.00 75.10
Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sda 0.00 22.50 0.00 82.17 0.00 1318.00 32.08 1.08 13.03 0.00 13.03 11.98 98.40
scd0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
(Sorry if the output doesn't line up)
It seems that on some of our systems any of the database updates are extremely disk intensive. It is curious that someone else would not see the slow behavior.
Software:
Debian 7.0.2, MySQL 5.5.31+dfsg-0+wheezy1, cqrlog 1.6.0-1
Hardware:
HP p7-1410, Intel Core i3 3.8GHz, 8GB RAM, Hitachi HDS72301 SATA drive.
My hardware is not ancient or slow, and the software is completely up to date.