Re: Django Web Hosting Service
Although more expensive ($34/mo), I found highspeedrails.com to be excellent--you can also host multiple sites on one account. As my webfaction sites grew, they didn't hold up the way that highspeedrails.com did. I eventually moved things over there. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
I have had two small Django sites running on asmallorange shared hosting for more thane a year. It took quite some time to get working in the shared environment, but then worked ok. The server reposne to the first hit on the site is slow to respond, but then ok. I just recently moved to a VPS account on linode.com, and am very happy so far with performance and low cost for a VPS option ($20/month). On Nov 25, 2:32 pm, LaundroMat <[EMAIL PROTECTED]> wrote: > I have had good experiences (albeit limited; the hosted site is more a > testing thing than something else at the moment) with a small orange > as well: asmallorange.com > > On Nov 21, 2:40 pm, "Ronaldo Z. Afonso" <[EMAIL PROTECTED]> > wrote: > > > > > Hi all, > > > Can anybody recommend me a Django Web Hosting Service? > > Thanks. > > > Ronaldo.- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
On Nov 26, 7:00 am, Jose C <[EMAIL PROTECTED]> wrote: > > In short, if you are running Django in worker MPM for Apache, you can > > be subject to sudden memory increases when you get concurrent requests > > against resources which chew up a lot of transient memory. Receiving a > > lot of concurrent POST requests with large content data can be one > > trigger if the framework reads such POST content all into memory at > > the same time. > > > As long as people want to run big Python web applications in memory > > constrained web hosting configurations, where Apache worker MPM with a > > small number of processes is the only viable solution for Apache, in > > contrast to prefork MPM which isn't, this is going to continue to be > > an issue. > > Graham > > Having recently come across Graham's comments on the Apache worker vs > prefork MPM on another framework group, and being a webfaction client, > I checked with webfaction which version they use. They use the > prefork version, so I'd suggest Kenneth look for other possible > reasons for his memory spikes in his app. Hmmm, are you sure they always use prefork? I'll admit I don't have first had experience with WebFaction, but given that they have a limit on the number of persistent processes you can have, this would be a severe restriction as it would limit the number of concurrent requests your overall application could handle quite drastically, as any spike in requests would require extra Apache child processes to be created. Thus, if you have a steady streams of requests, you would be stuck on your process limit quite quickly and so limit your throughput. I could understand them using prefork for the static file hosting, but for users own applications proxied behind their front end, using prefork doesn't make a great deal of sense to me as far as trying to use memory resources as efficiently as possible. Anyone else able to confirm how they setup the Apache instance which a users application runs in, not the main server used for static files? Irrespective of whether prefork is used instead of worker, in both cases there are a range of other issues that can also cause bloating in memory. With WSGI frameworks which use yield in some way, one such issue is where a user generator doesn't implement close() method for reclaiming resources immediately. As a consequence the reclaiming of resources can be deferred until the next GC cycle to try and break reference cycles between objects. Such reference count cycles can also occur in other situations as well, so not trying to clean up and aid garbage collection, by breaking cycles up front, can result in an accumulation of unreclaimed objects until the next time that GC runs. If other requests come in before GC kicks in, then total memory in use can end up growing more than one might expect. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
I have had good experiences (albeit limited; the hosted site is more a testing thing than something else at the moment) with a small orange as well: asmallorange.com On Nov 21, 2:40 pm, "Ronaldo Z. Afonso" <[EMAIL PROTECTED]> wrote: > Hi all, > > Can anybody recommend me a Django Web Hosting Service? > Thanks. > > Ronaldo. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
> In short, if you are running Django in worker MPM for Apache, you can > be subject to sudden memory increases when you get concurrent requests > against resources which chew up a lot of transient memory. Receiving a > lot of concurrent POST requests with large content data can be one > trigger if the framework reads such POST content all into memory at > the same time. > As long as people want to run big Python web applications in memory > constrained web hosting configurations, where Apache worker MPM with a > small number of processes is the only viable solution for Apache, in > contrast to prefork MPM which isn't, this is going to continue to be > an issue. > Graham Having recently come across Graham's comments on the Apache worker vs prefork MPM on another framework group, and being a webfaction client, I checked with webfaction which version they use. They use the prefork version, so I'd suggest Kenneth look for other possible reasons for his memory spikes in his app. My 2c on the original topic of this thread... I've been hosting with webfaction for 2 years and frequently monitor the resource usage on the shared machines hosting my sites and those of my clients (also on webfaction). Not once have any of the machines I monitor been under even moderate load, let alone heavy load - which to me speaks to their commitment to never push any of their machines to the max with user applications. Uptime has been over 99.9% for me and their support has been prompt and without fault to date. Cheers, JC --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
On Nov 25, 6:58 pm, David Sissitka <[EMAIL PROTECTED]> wrote: > Hello, > > > then why do you recommend that apache be restarted on 17,37 and 57 minutes? > > In fact *you* yourself install that cronjob on all django sites.? > > The cron job you're referring to: > > 1) Exists because if you've a spike in CPU or memory usage that > affects others on the same server your processes will be killed. If we > kill your processes the cron job ensures that your website won't be > down for too long. > 2) Only restarts your instance of Apache if it's down. > > > debug is false everywhere, apache is tweaked as per your recommendations > > and static media is served through the system wide apache. My client had to > > upgrade to 80 MB from 40 MB for a site that is 90% admin and has at the > > most, three users at a time. > > A memory leak isn't the only reason that your instance of Apache could > be using more than 40 MB of memory, off of the top of my head I can > think of nearly half a dozen reasons and I'm just WebFaction's Django > monkey. With that said the memory usage related Apache/Django tips > that we've in our blog are by no means a one size fits all solution > for decreasing Apache's memory usage. One should possibly heed my response to prior question about memory usage. http://groups.google.com.au/group/django-users/browse_frm/thread/7670886c04ac082d In short, if you are running Django in worker MPM for Apache, you can be subject to sudden memory increases when you get concurrent requests against resources which chew up a lot of transient memory. Receiving a lot of concurrent POST requests with large content data can be one trigger if the framework reads such POST content all into memory at the same time. The problem is that more often than not people don't understand the dynamics of how the underlying hosting system actually works and the implication of using multithreading. Thus, they tend to blame the hosting system, rather than taking preventative measures in their own application to avoid it. I believe that what is going to have to start happening is that the web frameworks themselves will have to start having protections built into them in some way to counter such problems. For example, the web framework could temporarily delay a POST request in a multithreaded server where there are already some specified number of requests already running, or the POST content size for existing requests has exceeded some set value. Similarly, where users know that specific URL handlers will consume a lot of transient memory, they need to be given a way of putting restrictions on the number of concurrent requests that might be allowed against that resource or such a group of resources at one time. As long as people want to run big Python web applications in memory constrained web hosting configurations, where Apache worker MPM with a small number of processes is the only viable solution for Apache, in contrast to prefork MPM which isn't, this is going to continue to be an issue. The only solutions are going to be to somehow have the web applications themselves throttle concurrent requests, or at least try and temper the issue with hosting solutions which allow more flexibility in defining how often web application processes should be recycled in order to reclaim memory, or which are able to themselves monitor memory usage and force process restarts when threshold values are exceeded. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
Hello, > then why do you recommend that apache be restarted on 17,37 and 57 minutes? > In fact *you* yourself install that cronjob on all django sites.? The cron job you're referring to: 1) Exists because if you've a spike in CPU or memory usage that affects others on the same server your processes will be killed. If we kill your processes the cron job ensures that your website won't be down for too long. 2) Only restarts your instance of Apache if it's down. > debug is false everywhere, apache is tweaked as per your recommendations and > static media is served through the system wide apache. My client had to > upgrade to 80 MB from 40 MB for a site that is 90% admin and has at the most, > three users at a time. A memory leak isn't the only reason that your instance of Apache could be using more than 40 MB of memory, off of the top of my head I can think of nearly half a dozen reasons and I'm just WebFaction's Django monkey. With that said the memory usage related Apache/Django tips that we've in our blog are by no means a one size fits all solution for decreasing Apache's memory usage. -David Sissitka --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
On 25-Nov-07, at 3:49 AM, David Sissitka wrote: >> I used to be very prowebfaction- they have huge memory leak >> problems and unless you stop and start apache once every 20 minutes, >> you very easily go over the memory limits. I now feel they are only >> good for toy sites. > > There are no known memory leaks in our Django stack, if you think > you've found one submit a support ticket and we'll be glad to look > into it. Every once in a while someone thinks they've found a memory > leak in our Django stack but nine tines out of ten the problem is that > they've DEBUG set to True in their settings.py. then why do you recommend that apache be restarted on 17,37 and 57 minutes? In fact *you* yourself install that cronjob on all django sites.? debug is false everywhere, apache is tweaked as per your recommendations and static media is served through the system wide apache. My client had to upgrade to 80 MB from 40 MB for a site that is 90% admin and has at the most, three users at a time. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ Foss Conference for the common man: http://registration.fossconf.in/web/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
Kenneth Gonsalves wrote: > > On 22-Nov-07, at 2:15 AM, Daniel Roseman wrote: > >>> http://www.webfaction.com/ >>> >>> They are amazing and reasonably priced. Their support is great. They >>> have exceeded my expectations many times. >>> >>> Chuck >> Second this recommendation. I am very happy with them, and they have >> responded to support calls nearly instantly. > > I used to be very pro webfaction - they have huge memory leak > problems and unless you stop and start apache once every 20 minutes, > you very easily go over the memory limits. I now feel they are only > good for toy sites. > Purely anecdotal, but this doesn't match my experience with Webfaction at all - I'm currently doing some updates on a site I hadn't touched for a while - when I logged in to dump the database contents for development purposes, I noticed that my previous shell login was almost a full year ago. The site was running perfectly fine and within its memory limits for that whole time period without me having to do any administration work. Same thing with the other site I currently host there - both are using the "Shared 1" option. Jonathan. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
On Nov 22, 1:09 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > I used to be very prowebfaction- they have huge memory leak > problems and unless you stop and start apache once every 20 minutes, > you very easily go over the memory limits. I now feel they are only > good for toy sites. There are no known memory leaks in our Django stack, if you think you've found one submit a support ticket and we'll be glad to look into it. Every once in a while someone thinks they've found a memory leak in our Django stack but nine tines out of ten the problem is that they've DEBUG set to True in their settings.py. -David Sissitka --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
On 22-Nov-07, at 2:15 AM, Daniel Roseman wrote: >> http://www.webfaction.com/ >> >> They are amazing and reasonably priced. Their support is great. They >> have exceeded my expectations many times. >> >> Chuck > > Second this recommendation. I am very happy with them, and they have > responded to support calls nearly instantly. I used to be very pro webfaction - they have huge memory leak problems and unless you stop and start apache once every 20 minutes, you very easily go over the memory limits. I now feel they are only good for toy sites. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
Yeah, Slicehost have a nice name in the industry, though you gotta order with some time in advance. Don't rely on them for "I need a server for yesterday" situations ;) ~ Chris El jue, 22-11-2007 a las 04:37 -0800, [EMAIL PROTECTED] escribi�: > > > Can anybody recommend me a Django Web Hosting Service? > > I recommend buying a VPS, and one of the very best VPS services is > slicehost.com which i really recommend! > If VPS is to expensive for you then WebFaction is the solution you > should go with. > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
> Can anybody recommend me a Django Web Hosting Service? I recommend buying a VPS, and one of the very best VPS services is slicehost.com which i really recommend! If VPS is to expensive for you then WebFaction is the solution you should go with. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
> Can anybody recommend me a Django Web Hosting Service? Webfaction is really good. I'm a happy customer. \Niels --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
Another +1 for webfaction. The cheapest plan supports Django, 7.50/mo for two years in advance, but you can get a refund for your remaining time if you're not satisfied. Pretty sweet deal. On 11/21/07, Daniel Roseman <[EMAIL PROTECTED]> wrote: > > > On Nov 21, 1:57 pm, cwurld <[EMAIL PROTECTED]> wrote: > > http://www.webfaction.com/ > > > > They are amazing and reasonably priced. Their support is great. They > > have exceeded my expectations many times. > > > > Chuck > > Second this recommendation. I am very happy with them, and they have > responded to support calls nearly instantly. > -- > DR. > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
On Nov 21, 1:57 pm, cwurld <[EMAIL PROTECTED]> wrote: > http://www.webfaction.com/ > > They are amazing and reasonably priced. Their support is great. They > have exceeded my expectations many times. > > Chuck Second this recommendation. I am very happy with them, and they have responded to support calls nearly instantly. -- DR. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
I'm enrolled in the Media Temple Django Container Beta Testing programm, and so far, it's an absolute killer. They've been working close with the Django guys to make it somewhat the "official" django hoster. The django site itself is hosted on a media temple server. Though they're still in Beta, and not publicly available, you could try to ask them if you could get a container to try it. You'll need a grid server account, though. Good Luck. ~ Chris El mi�, 21-11-2007 a las 05:57 -0800, cwurld escribi�: > http://www.webfaction.com/ > > They are amazing and reasonably priced. Their support is great. They > have exceeded my expectations many times. > > Chuck > > On Nov 21, 7:40 am, "Ronaldo Z. Afonso" <[EMAIL PROTECTED]> > wrote: > > Hi all, > > > > Can anybody recommend me a Django Web Hosting Service? > > Thanks. > > > > Ronaldo. > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Web Hosting Service
http://www.webfaction.com/ They are amazing and reasonably priced. Their support is great. They have exceeded my expectations many times. Chuck On Nov 21, 7:40 am, "Ronaldo Z. Afonso" <[EMAIL PROTECTED]> wrote: > Hi all, > > Can anybody recommend me a Django Web Hosting Service? > Thanks. > > Ronaldo. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Django Web Hosting Service
Hi all, Can anybody recommend me a Django Web Hosting Service? Thanks. Ronaldo. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
