<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>selfoss support forum - SQLite time-consuming feed update (2.12 warning)</title>
<link>https://forum.selfoss.aditu.de/</link>
<description>selfoss support forum</description>
<language>en</language>
<item>
<title>SQLite time-consuming feed update (2.12 warning)</title>
<content:encoded><![CDATA[<p>Hello,</p>
<p>I have just upgraded from 2.9 to 2.12 and noticed the feed update to be very slow.<br />
On my Samsung 830 SSD, I saw 100% disk usage with 500 write requests with 2ms average time (=1s) every second.</p>
<p>Tracking with DEBUG option, I got the following at the end (note: 4000 entries and 7MB database on SSD):<br />
09-17-14 13:55:46 Debug cleanup orphaned and old items<br />
09-17-14 13:55:46 Debug cleanup orphaned and old items finished<br />
09-17-14 13:55:46 Debug delete orphaned thumbnails<br />
09-17-14 13:55:46 Debug delete orphaned thumbnails finished<br />
09-17-14 13:55:46 Debug delete orphaned icons<br />
09-17-14 13:55:46 Debug delete orphaned icons finished<br />
<strong>09-17-14 13:55:46 Debug optimize database<br />
09-17-14 13:58:14 Debug optimize database finished</strong></p>
<p>That is 2'30&quot; of normal update which I run hourly. During this time, no other selfoss page is server (browser just waits).</p>
<p>I have commented the body of optimize function for myself (daos/sqlite/Database.php) since it was empty in 2.9.</p>
<p>But since it takes so long for my case, I don't think it's a good idea to use it this way, especially since people who actually need this optimization will be impacted even worse.</p>
<p>Note: my DB has shrunk with this code from 10M (2.9 backup) to 7MB after about a year.</p>
]]></content:encoded>
<link>https://forum.selfoss.aditu.de/index.php?id=926</link>
<guid>https://forum.selfoss.aditu.de/index.php?id=926</guid>
<pubDate>Wed, 17 Sep 2014 14:27:22 +0000</pubDate>
<dc:creator>mathew7</dc:creator>
</item>
</channel>
</rss>
