Hi!
Thanks for the description. What I want and I believe is needed is a
generic queue that is not engine specific. No ugly locking either or
thread specific.
A nice blueprint on this would be awesome.
Cheers,
--Brian
On Aug 26, 2008, at 9:00 PM, Brian Moon <[EMAIL PROTECTED]> wrote:
Brian Aker wrote:
Hi!
Delayed is broken in a number of ways. What is your use case?
At dealnews, we use it primarily as an asynchronous logging system.
For example, when a user clicks on a deal on dealnews, we don't want
that click tracking process to hamper the user getting to the
destination site. So, we have a very low mysql connection timeout
and we use insert delayed. We have about a 5% loss due to either a
connection timeout or an unknown failed log. But, that is ok for
this use case. We are comparing one deal's performance to another.
They all have the same approximate loss rate.
In Phorum, we use INSERT DELAYED when inserting data into our search
table. The table has a FullText key on it and during high load that
insert can be expensive. Because most users do not search for
something they just posted, it is ok to let the insert into the
search table lag a bit behind other data. We have a search repair
feature for search tables that are missing messages. We don't want
to have the FullText on the main messages table as that would limit
that table to MyISAM. Phorum does much better with InnoDB, except
for search.
Did you mean this to go to the list?
--
Brian Moon
Senior Web Engineer
------------------------------
When you care enough to spend the very least.
http://dealnews.com/
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
