phpgroupware-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Phpgroupware-developers] SQL Stored procedures?


From: Jason Wies
Subject: Re: [Phpgroupware-developers] SQL Stored procedures?
Date: Thu, 23 May 2002 12:44:28 -0400
User-agent: Mutt/1.2.5i

Another performance improvement we should look towards adding is allowing for 
multiple database servers.  With MySQL, it's cake to add a read-only slave 
(http://mysql.com/documentation/mysql/bychapter/manual_MySQL_Database_Administration.html#Replication).
  This provides an economical way to scale, and allows for high availability.

In the code, we'd only have to randomly choose the database server when 
creating the class in order to switch read servers.  Write queries need to be 
split from read queries, which isn't being done now, but that could be changed 
with a search and replace script.

If anyone has experience with Postgres, Oracle, etc. replication, I would be 
interested to know if they work the same way.  I suspect Oracle might be able 
to redirect queries, in which case nothing extra would be needed to support it.

Jason Wies aka Zone

On Thu, May 23, 2002 at 07:14:22AM -0700, Dan Kuykendall (Seek3r) wrote:
> Roy Sigurd Karlsbakk wrote:
> > 
> > > it might, but it would not only take major additions to the setup code to
> > > support it, but would require most apps to be rewritten to call sp's
> > > instead of executing sql, thus totaly defeating the database abstraction.
> > > The whole idea behind phpgwapi's database class is that the app programmer
> > > doesn't need to care what database is behind it, he/she just uses standard
> > > SQL statements.  And if this is followed, the app will magically work on
> > > all databases that phpgw supports without furthur porting.
> > 
> > sure. but today's design is SLOW and doesn't scale above a few number of
> > concurrent users
> 
> There are ways to improve performance without using stored procedures.
> Also after years of DB admin responsibilties I have learned well that
> SP's are not a magic bullet for performance. Their biggest benefit is in
> centralzing control over data access and retrieval, NOT performance. In
> some cases they will improve performance a little, but thats not where I
> feel they are valuable.
> 
> Also to say that phpGW can only handle a few concurrent users is a joke.
> I have an install at a public school that runs on a P133 with 128MB. It
> runs RedHat with PHP4. I have it setup to use PHP4 sessions and
> phpgwinfo array caching. The box is regularly in use by 60+ students and
> facilty concurrently.
> The phpgroupware.org demo is also hit hard during releases and is
> running on a fairly small server as well.
> 
> We are always looking for ways to increase performance and if you have
> ideas, present them so that we can look at the merits and if they are
> good we would look at implementing them.
> 
> Dan Kuykendall
> 
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/phpgroupware-developers



reply via email to

[Prev in Thread] Current Thread [Next in Thread]