Re: Controlling Threads

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

 



Hi, Bruno...

Based on what I had presented so far, You are right in Your suggestion, but
historically, the DB was already installed on the same machine. And the
problem was the same... just that the first machine was a Celeron 700MHz
with 256MB RAM. With this entire freezing scenario, I was able to allocate
the actual machine (a P4, 2,4MHz, 1GB RAM) to run GK, but not the MySQL 4.0
used as backend. I'm planning to migrate not only the DB to the GK machine,
but also process a version upgrade.

So, I can say that this problem is just the same, no matter where the DB is
located... I agree that if closer, better... The actual machine was once
used as a proxy between our VoIP network and termination providers and the
problems (with MySQL 4.0 on localhost) arise every time the current calls
grow to something around 80-90 calls... but now the problem initiate on just
8-10 concurrent calls and around 2-3 cps...

As a result from all this discussion, I come understand that this problem
can be 'mapped' based on some sort of equation that has cps, current calls
being updated and calls duration. So I ask again: if my "equation" is
correct than where is the middle-point to make it work? Where can I find
some test procedure to be able to define the maximum load from all my
systems?

Edson.

> -----Original Message-----
> From: openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-
> users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Bruno Lopes de Souza
> Benchimol
> Sent: quinta-feira, 3 de agosto de 2006 20:28
> To: 'GNU Gatekeeper Users'
> Subject: Re:  Controlling Threads
> 
> After reading the post by Michal, I would suggest you a little effort on
> trying the following: move the database to the local machine.
> 
> Anyway you probably going to tell me that's not possible and other stuff,
> but think about the following scenario:
> 
> A database on the local machine, replicating to the remote site,
> asynchronally, this way it will not hang up trying to "commit" the tables
> on
> both sites, so you get fast response on accounting and the database will
> carry itself handling the replication over the slow link.
> 
> That might solve your problem, worth a try. Btw, which database you using?
> 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________________

Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux