From: | "Andrej Ricnik-Bay" <andrej(dot)groups(at)gmail(dot)com> |
---|---|
To: | "Sean Davis" <sdavis2(at)mail(dot)nih(dot)gov> |
Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Math Operations - DB or App? |
Date: | 2006-05-09 21:55:37 |
Message-ID: | b35603930605091455u3554e13eq526c32b57dee32e7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 5/10/06, Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> wrote:
> > With which operations/what number of calculations does
> > the CPU load on the server become a problem, though (compared
> > to the network-traffic caused by having it on the client-side)? I can
> > think of a few applications/implementations that I wouldn't want to
> > be running on the server - where to draw the line?
> I would imagine that the answer is very complicated. There are a lot of
> details in application design that are being ignored by my answer above.
> For example, can data be cached effectively on the client side (or in a web
> app, on the webserver)? Is the app DB intensive (lots of concurrent
> read/writes) or are there monstrous queries running on the DB all the time
> (data mining app, for example)? There are many points that do and should
> influence application design, so benchmarking, knowing user needs, hardware
> and software constraints, and maintainability all play into the answer, I
> think.
>
> Not an answer, I know....
I wouldn't say that :} ... it's pretty much exactly what I was hoping for,
namely that there *IS* no answer, and that it always depends on varied
factors which need to be evaluated for each individual case.
> Sean
Cheers,
Andrej
--
Please don't top post, and don't use HTML e-Mail :} Make your quotes concise.
From | Date | Subject | |
---|---|---|---|
Next Message | operationsengineer1 | 2006-05-09 22:17:53 | Re: Math Query Help |
Previous Message | Sean Davis | 2006-05-09 21:51:56 | Re: Math Operations - DB or App? |