If it's just disk performance and ability to add on space, a simple
performance RAID (JBOD or RAID-0) attached internally, externally via
Firewire/eSATA, or as NAS from another machine. If you're worried
about a lot of files moving down the network concurrently, then you'll
certainly have to look i
On Sun, Dec 26, 2010 at 1:40 AM, Andy wrote:
> Planning ahead, if the website gets popular, how do I scale it out so
> that the images (both original and thumbnails) will be stored in and
> served from multiple servers? Maybe a cluster? Is there any open
> source software that would help me in thi
I'm building a website where users can upload photos and I'd also
convert uploaded photos into thumbnails (probably using sorl-
thumbnail).
When everything fits in one server, I would just use FileField() and
handle_uploaded_file() as detailed in the doc.
Planning ahead, if the website gets popul
Tim,
Thanks for the helpful answers.
As for specific details about my app, right now I'm still in the
design phase. It will start small, but hopefully it will get popular
quickly. So I don't know how big the Db will be or how many users will
there be.
What I'm trying to do is to make sure there
> Recently I found out Django doesn't support multiple databases. That's
> quite surprising.
>
> Given that limitation, how do you scale out a Django app?
Depends on where your bottleneck(s) is/are. It also depends
heavily on your read/write usage pattern. If you're truly
experiencing a sten
Recently I found out Django doesn't support multiple databases. That's
quite surprising.
Given that limitation, how do you scale out a Django app?
Without multi-DB support, most of the usual techniques for scaling out
such as:
- DB sharding
- functional partitioning - eg. separate DB serve
On 10/4/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
> JB> You mean no projects using MySQL Replication,
>
> Did I? I think I've said exactly opposite.
You jumped from "MySQL Replication won't work" to "no big projects
will use Django". Big projects already are using Django, therefore th
James,
JB> On 10/3/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
>> The only thing django app should know is that there are two different
>> *kinds* of servers: read-only and whole access. It doesn't matter how many
>> servers you have - you may well have pool of masters and pool of sl
AA> Am 03.10.2007 um 12:36 schrieb Andrey Khavryuchenko:
AA> It's possible to use circular replication together with some free
AA> load balancing software.
As I've told earlier, I know perfectly about circular replication.
AA> Then there's MySQL Proxy that allows you to manipulate queri
Check out: http://ant.apache.org/
These types of deployment & initialization tasks should be handled by
the surrounding environment, not Django itself. I suggest you use ant
or something similar to set up some scripts for yourself that
coordinate everything.
--~--~-~--~~--
Am 03.10.2007 um 12:36 schrieb Andrey Khavryuchenko:
> I know about MySQL Cluster. The obvious disadvantage is that the
> whole
> database should be in main memory. Kiss goodbye to a bunch of cheap
> servers sitting close to actual users.
>
> There are also replication tweaks like multi-mast
On 10/3/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
> The only thing django app should know is that there are two different
> *kinds* of servers: read-only and whole access. It doesn't matter how many
> servers you have - you may well have pool of masters and pool of slaves, it
> doesn't
JB> On 10/2/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
>> Shouldn't it? In case of MySQL replication (which is quite widely used)
>> and transactions someone somehow *has* to decide where the whole
>> transaction is going - to a master or to a slave.
JB> In the case of MySQL, use
On 10/2/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
> Shouldn't it? In case of MySQL replication (which is quite widely used)
> and transactions someone somehow *has* to decide where the whole
> transaction is going - to a master or to a slave.
In the case of MySQL, use MySQL Cluster, wh
JB> As for database clustering, there's a philosophical issue here: Django
JB> shouldn't need to know whether there's one database server behind it,
JB> or five, or a hundred.
Shouldn't it? In case of MySQL replication (which is quite widely used)
and transactions someone somehow *has* to de
On Sun, 2007-09-30 at 20:37 -0500, James Bennett wrote:
> On 9/30/07, Mark Green <[EMAIL PROTECTED]> wrote:
> > I'm not sure what drove me to call it "fragment caching".
> > What I really meant to point at are the little things (such as
> > form_for_model()) that would likely benefit from some obj
On Sun, 2007-09-30 at 20:29 -0500, James Bennett wrote:
> On 9/30/07, Mark Green <[EMAIL PROTECTED]> wrote:
> > My question was really only about the former, a much simpler problem:
> > How to keep a tcp connection persistent and re-use it across requests?
>
> By using a pooling connection manage
On 9/30/07, Mark Green <[EMAIL PROTECTED]> wrote:
> I'm not sure what drove me to call it "fragment caching".
> What I really meant to point at are the little things (such as
> form_for_model()) that would likely benefit from some object
> caching instead of burning cycles for each request.
You c
On 9/30/07, Mark Green <[EMAIL PROTECTED]> wrote:
> My question was really only about the former, a much simpler problem:
> How to keep a tcp connection persistent and re-use it across requests?
By using a pooling connection manager external to Django. Again,
complicating the application layer wi
On Sun, 2007-09-30 at 16:16 -0500, James Bennett wrote:
> On 9/30/07, Mark Green <[EMAIL PROTECTED]> wrote:
> > Hm, this raises some serious scalabity questions for me.
> > >From your description it sounds like there is no template
> > fragment caching, not even db connection pooling possible
> >
On 9/30/07, Mark Green <[EMAIL PROTECTED]> wrote:
> Hm, this raises some serious scalabity questions for me.
> >From your description it sounds like there is no template
> fragment caching, not even db connection pooling possible
> with django?
You can cache anything you want to cache; read the c
On Fri, 2007-09-28 at 22:29 -0500, James Bennett wrote:
> On 9/28/07, Mark Green <[EMAIL PROTECTED]> wrote:
> > i'm looking for a way to perform a bunch of initialization tasks
> > right after django startup.
>
> There really is no such thing as "Django startup"; remember that
> Django is hosted
22 matches
Mail list logo
