From: | Vick Khera <vivek(at)khera(dot)org> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Queues Problem |
Date: | 2010-06-08 17:18:59 |
Message-ID: | AANLkTikmW9r1Eo1JxJJ2h80kIR9EtTg3GEYfsm73uwZx@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jun 8, 2010 at 12:53 PM, uaca man <uacaman(at)gmail(dot)com> wrote:
> Lets say for a 20 thousand users server, it may have at most 20 thousand
> constructions started at the same time.
>
> To accomplish such behavior so far I could come up with two options:
>
> 1. Make a never ending function that will look at the BuildingQueue
> table every second and finish the construction.
>
> 2. Every time the user start a construction add a cron job for that
> construction to run 1 seconds after the construction is finished and call a
> function the will finish.
You should investigate a proper queueing or job scheduling solution,
such as RabbitMQ or Qpid or gearman. They are designed for this type
of requirement. You will have to write your code to be more event
driven, and make the web server just generate requests and view the
results where they are stored.
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2010-06-08 17:41:01 | Re: Queues Problem |
Previous Message | uaca man | 2010-06-08 16:53:34 | Queues Problem |