Naturally when working with a large database, the program requires some tweaks (in contrast to its default configuration), because when the database approaches some undetermined size (which I never made a mental note of), the program will start to malfunction when trying to launch the program (because it will run out of memory). However, it should be noted that I do still experience corruption issues IF the computer crashes or if the power goes out BUT RSSOwlnix has a command line REPAIR function for the database!! This has saved my data more times than I can count. Then I switched to RSSOwlnix and I no longer have the lag issues while searching, and large database files of 2GB+ is no longer an issue either – as it is perfectly capable of handling extremely large database files without any performance and/or corruption issues. This was a huge inconvenience for me, because I essentially lost all my data. There is no function to repair the database built into the program that I know of, and I could find no information anywhere online on how to repair database via any other method (even on the user forums). Other than the search is extremely laggy/slow with a very large index > I learned that the program has a tendency for the database to corrupt when the database size gets around 2GB - also the database has a tendency to corrupt if (while the program is running) the computer crashes, power goes out (etc). Previously I tried to use QuiteRSS for the better part of about 1 year, and I have some miscellaneous complaints that others might consider if they have a lot of sites indexed which might generate a large database. FYI this many sites will produce a database size of around 4-6GB per year (depending on how much content is generated). I have around 800 sites indexed via RSS, and I export the database each year to archive each years feeds.
This program, while discontinued, has been forked to RSSOwlnix which is under active development:
0 kommentar(er)
