<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>Autarchy of the Private Cavegodaddy &#187;</title> <atom:link href="http://bogdan.org.ua/tags/godaddy/feed" rel="self" type="application/rss+xml" /><link>http://bogdan.org.ua</link> <description>Tiny bits of bioinformatics, [web-]programming etc</description> <lastBuildDate>Fri, 03 Feb 2012 22:51:18 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Less than an hour of GoDaddy MySQL5 database downtime today</title><link>http://bogdan.org.ua/2008/03/26/less-than-an-hour-of-godaddy-mysql5-database-downtime-today.html</link> <comments>http://bogdan.org.ua/2008/03/26/less-than-an-hour-of-godaddy-mysql5-database-downtime-today.html#comments</comments> <pubDate>Wed, 26 Mar 2008 13:04:08 +0000</pubDate> <dc:creator>Bogdan</dc:creator> <category><![CDATA[Misc]]></category> <category><![CDATA[downtime]]></category> <category><![CDATA[godaddy]]></category> <category><![CDATA[mysql]]></category> <category><![CDATA[PHP]]></category> <guid
isPermaLink="false">http://bogdan.org.ua/2008/03/26/less-than-an-hour-of-godaddy-mysql5-database-downtime-today.html</guid> <description><![CDATA[Must have been some maintenance, as I didn&#8217;t notice any changes in PHP/MySQL versions since the 7th of March. Update: it seems as though since that short MySQL outage everything is faster at GoDaddy shared hosting. Did they upgrade database server(s)? I have no idea, but I like the change.]]></description> <content:encoded><![CDATA[<p>Must have been some maintenance, as I didn&#8217;t notice any changes in PHP/MySQL versions since the 7th of March.</p><p><ins
datetime="2008-04-06T07:01:54+00:00">Update:</ins> it seems as though since that short MySQL outage everything is faster at GoDaddy shared hosting. Did they upgrade database server(s)? I have no idea, but I like the change.</p> ]]></content:encoded> <wfw:commentRss>http://bogdan.org.ua/2008/03/26/less-than-an-hour-of-godaddy-mysql5-database-downtime-today.html/feed</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>GoDaddy: undocumented 20-second CPU time maximal execution limit? (python, ELF, etc)</title><link>http://bogdan.org.ua/2007/10/16/godaddy-undocumented-20-second-cpu-time-maximal-execution-limit-python-elf.html</link> <comments>http://bogdan.org.ua/2007/10/16/godaddy-undocumented-20-second-cpu-time-maximal-execution-limit-python-elf.html#comments</comments> <pubDate>Tue, 16 Oct 2007 10:32:17 +0000</pubDate> <dc:creator>Bogdan</dc:creator> <category><![CDATA[*nix]]></category> <category><![CDATA[Misc]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Web]]></category> <category><![CDATA[behaviour]]></category> <category><![CDATA[CPU]]></category> <category><![CDATA[godaddy]]></category> <category><![CDATA[hosting]]></category> <category><![CDATA[killed]]></category> <category><![CDATA[linux]]></category> <category><![CDATA[problem]]></category> <category><![CDATA[script]]></category> <category><![CDATA[server]]></category> <category><![CDATA[shared]]></category> <guid
isPermaLink="false">http://bogdan.org.ua/2007/10/16/godaddy-undocumented-20-second-cpu-time-limit-on-all-executables-python-elf-etc.html</guid> <description><![CDATA[Today, setting up a relatively serious (in CPU resources needed) web-system, I ran into a weird problem of python scripts ending prematurely. After some investigation, it looked like any process which uses up more than 20 seconds of CPU time, is automatically killed. To verify this, I wrote an infinite loop in C, PLAIN TEXT [...]]]></description> <content:encoded><![CDATA[<p>Today, setting up a relatively serious (in CPU resources needed) web-system, I ran into a weird problem of python scripts ending prematurely. After some investigation, it looked like any process which uses up more than 20 seconds of CPU time, is automatically killed. To verify this, I wrote an infinite loop in C,</p><div
class="igBar"><span
id="lc-2"><a
href="#" onclick="javascript:showPlainTxt('c-2'); return false;">PLAIN TEXT</a></span></div><div
class="syntax_hilite"><span
class="langName">C:</span><div
id="c-2"><div
class="c"><ol><li
style="font-family: 'Courier New', Courier, monospace; color: black; font-weight: normal; font-style: normal;color:#3A6A8B;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;"><span
style="color: #993333;">int</span> main <span
style="color: #66cc66;">&#40;</span><span
style="color: #66cc66;">&#41;</span> <span
style="color: #66cc66;">&#123;</span></div></li><li
style="font-weight: bold;color:#26536A;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;">&nbsp;<span
style="color: #993333;">unsigned</span> <span
style="color: #993333;">int</span> i;</div></li><li
style="font-family: 'Courier New', Courier, monospace; color: black; font-weight: normal; font-style: normal;color:#3A6A8B;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;">&nbsp;</div></li><li
style="font-weight: bold;color:#26536A;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;">&nbsp;<span
style="color: #b1b100;">for</span> <span
style="color: #66cc66;">&#40;</span>i = <span
style="color: #cc66cc;color:#800000;">0</span>; i &lt;<span
style="color: #cc66cc;color:#800000;">2</span> ; i++ <span
style="color: #66cc66;">&#41;</span> <span
style="color: #66cc66;">&#123;</span></div></li><li
style="font-family: 'Courier New', Courier, monospace; color: black; font-weight: normal; font-style: normal;color:#3A6A8B;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;">&nbsp; i = <span
style="color: #cc66cc;color:#800000;">0</span>;</div></li><li
style="font-weight: bold;color:#26536A;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;">&nbsp;<span
style="color: #66cc66;">&#125;</span></div></li><li
style="font-family: 'Courier New', Courier, monospace; color: black; font-weight: normal; font-style: normal;color:#3A6A8B;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;">&nbsp;</div></li><li
style="font-weight: bold;color:#26536A;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;">&nbsp;<span
style="color: #b1b100;">return</span> <span
style="color: #cc66cc;color:#800000;">0</span>;</div></li><li
style="font-family: 'Courier New', Courier, monospace; color: black; font-weight: normal; font-style: normal;color:#3A6A8B;"><div
style="font-family: 'Courier New', Courier, monospace; font-weight: normal;"><span
style="color: #66cc66;">&#125;</span></div></li></ol></div></div></div><p></p><p>compiled it and executed several times on the GoDaddy shared hosting server. I did observe the program running for the maximum of 20 seconds of CPU time, not a second more. Please note, that 20 seconds of CPU time can be much more of "real" time, if the script isn't using 100% of CPU, which often the case for shared hosting. Thus if you have in your php.ini max_execution_time set to, say, 60 seconds, your php script may actually execute as long as one minute; but I'm pretty sure that if your script has lots of CPU-intensive procedures, then as soon as it uses 20 seconds of CPU time, it will be terminated (however, this statement still needs checking - anyone?).</p><p>To verify, I also created a cron job with the same file. It ran for 30 seconds CPU time.</p><p>Strangely, this behaviour is not documented anywhere.</p><p>This limit may also explain a number of other problems, if you have heavy web-applications: they just might be killed before they are finished, causing errors.</p><p>I do understand the reason for this limitation, and am sure similar limitations exist in other shared hosting environments. The only important thing here is that this limit should have been documented and even put upfront somewhere in the hosting plans descriptions.</p><p>I also wonder if the limit is the same for all godaddy shared hosting plans, or if it differs. 20 seconds when executed from PHP, and 30 seconds when executed as a cron job were observed on the Deluxe Linux Hosting plan.</p><p>Extensions, additions and comments are welcome.</p> ]]></content:encoded> <wfw:commentRss>http://bogdan.org.ua/2007/10/16/godaddy-undocumented-20-second-cpu-time-maximal-execution-limit-python-elf.html/feed</wfw:commentRss> <slash:comments>17</slash:comments> </item> <item><title>GoDaddy shared hosting: too slow?</title><link>http://bogdan.org.ua/2007/03/12/godaddy-shared-hosting-too-slow.html</link> <comments>http://bogdan.org.ua/2007/03/12/godaddy-shared-hosting-too-slow.html#comments</comments> <pubDate>Mon, 12 Mar 2007 15:50:10 +0000</pubDate> <dc:creator>Bogdan</dc:creator> <category><![CDATA[Misc]]></category> <category><![CDATA[Web]]></category> <category><![CDATA[godaddy]]></category> <category><![CDATA[hosting]]></category> <category><![CDATA[shared]]></category> <category><![CDATA[slow]]></category> <guid
isPermaLink="false">http://www.bogdan.org.ua/2007/03/12/godaddy-shared-hosting-too-slow.html</guid> <description><![CDATA[Note: have a look at other hosting options. Update 7: I'm now quite satisfied with page generation times. See other updates at the end of the post and comments to find out more. Update 8: this blog is not at godaddy anymore for the reasons which have nothing to do with speed. I'm currently using [...]]]></description> <content:encoded><![CDATA[<p><em>Note: have a look at</em> <a
href="http://bogdan.org.ua/blog-hosting">other hosting options</a>.</p><p><ins
datetime="2008-09-03T11:34:27+00:00">Update 7:</ins> I'm now quite satisfied with page generation times. See other updates at the end of the post and comments to find out more.<br
/> <ins
datetime="2009-02-02T17:40:42+00:00">Update 8:</ins> this blog is not at godaddy anymore for the reasons which have nothing to do with speed.</p><p>I'm currently using GoDaddy shared hosting plan. I noticed that my blog, as it grows in popularity and visitors, displays a wide range of page-response times. The best I had seen so far was below 3 seconds of page generation time (note: _not_ page loading, but page generation). If it were the average, I would be happy. However, much more frequently observed times are in range of 20-30 seconds per page. Sometimes pages even timeout, as my uptime tracker service is reporting (For February, there were 100 minutes of unresponsive pages, for March - already over 10 hours!!!).</p><p>For example, today around 16:00 GMT the following statistics were reported by my blog:</p><blockquote><p> 22 queries.<br
/> 33.416 seconds.</p></blockquote><p>Evidently, this is unacceptably slow.<br
/> <span
id="more-131"></span><br
/> Based on that same tracker, when plain-html file was tracked, no downtime was observed. It was only after I started tracking the PHP-generated file, that "downtimes" became obvious. Evidently, CPU is not powerful enough to handle all the processing from multiple shared-hosting accounts at GoDaddy server(?s), thus time-outs are observed.</p><p>I used the <a
href="http://www.domaintools.com/research/reverse-ip/">reverse-IP</a> tool from domaintools.com to find out, that</p><blockquote><p> There are 3707 domains hosted on this IP address.<br
/> Here are a few of them:</p><p> 1. 100-downloads.com<br
/> 2. 101artisanlane.com<br
/> 3. 107threnegades.net</p></blockquote><p>(Well, with 100GB storage and 1TB traffic I think I could have the 100-downloads-like web-site, but only based on pure-html pages, with no scripting at all. With scripting, that would be a dead site, deducing from my blog's page generation speeds.)</p><p>(You could also try an alternative <a
href="http://www.ip-adress.com/reverse_ip">reverse-IP tool</a>)</p><p>I will contact GoDaddy support with the "slow page generation, low CPU?" question to see if anything can be done. So far I'm satisifed with GoDaddy, even as my demands continue to grow since 2005. With static pages I think there would be no problems, but who uses static pages nowadays?</p><p>Meanwhile, I found the <a
href="http://secure.hostican.com/cgi-bin/affiliates/clickthru.cgi?id=chronos&#038;campaign=bogdanorgua_slowgodaddy">Linux Tera-Host hosting plan</a> from hostican attractive, as for 10$/month. Well, "unlimited bandwidth" does look slightly suspicious, as it can be 40kbit/sec "unlimited" <img
src='http://bogdan.org.ua/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . Please comment if you had any previous experience with hostican... or with decreasing page-generation times on GoDaddy shared hosting.</p><p><ins
datetime="2007-03-18T07:59:10+00:00">Update:</ins> after I contacted GoDaddy support with "slow page generation", the page generation speed actually increased. So far the timings for a single page generation are within 1-10 seconds, and I do not get any more "downtimes" in my hosting uptime tracker. However, communication with support did not reveal anything new concerning my question. As long as page generation times do not increase, I'll archive and forget about this problem. (...doubting that any other shared hosting provider will ensure enough CPU to get less-than-a-second-per-page times.)</p><p><ins
datetime="2007-10-19T14:15:41+00:00">Update 2:</ins> there's also more <a
href="http://bogdan.org.ua/2007/10/16/godaddy-undocumented-20-second-cpu-time-maximal-execution-limit-python-elf.html">important information about GoDaddy hosting</a>, namely about their scheme of preventing one shared hosting user eating up 100% of system resources.</p><p><ins
datetime="2008-01-31T07:46:59+00:00">Update 3:</ins> as of January 31, 2008, there are 2924 domains hosted on my shared hosting server (according to <a
href="http://www.domaintools.com/research/reverse-ip/">reverse-IP tool</a>).</p><p><ins
datetime="2008-04-06T07:06:45+00:00">Update 4:</ins> as of April 6, 2008, there are 2834 domains hosted on the server with the same IP as mine. I must add that it seems as though since that <a
href="http://bogdan.org.ua/2008/03/26/less-than-an-hour-of-godaddy-mysql5-database-downtime-today.html">short MySQL outage</a> everything is faster at GoDaddy shared hosting. Did they upgrade database server(s)? I have no idea, but I like the change.</p><p><ins
datetime="2008-06-03T10:01:01+00:00">Update 5:</ins> as of June 3, 2008, there are 2754 domains hosted on my shared hosting server at GoDaddy.</p><p><ins
datetime="2008-07-16T08:46:12+00:00">Update 6:</ins> as of July 16, 2008, there are 2697 domains hosted on my shared hosting server at GoDaddy. Moreover, the Deluxe shared hosting plan now has 1.5 times higher disk and bandwidth limits, and 5 times more FTP users per account. Page generation times have improved noticeably, though some slowdowns in the peak hours can be still observed.</p> ]]></content:encoded> <wfw:commentRss>http://bogdan.org.ua/2007/03/12/godaddy-shared-hosting-too-slow.html/feed</wfw:commentRss> <slash:comments>55</slash:comments> </item> </channel> </rss>
