Archiveopteryx vs. Cyrus

Posted Mar 18, 2010 14:16 UTC (Thu) by nye (subscriber, #51576)
In reply to: Archiveopteryx vs. Cyrus by dlang
Parent article: Archiveopteryx

The FAQ says:

"Archiveopteryx's bottleneck is the number of deliveries per minute, everything else is irrelevant. ... On fast PC hardware, Archiveopteryx currently handles in the neighbourhood of 4000 deliveries per minute."

Of course, that doesn't directly answer your question...

to post comments

Archiveopteryx vs. Cyrus

Posted Mar 18, 2010 18:07 UTC (Thu) by dlang (guest, #313) [Link]

Actually, that makes me suspicious that they have not really scaled this up.

if a user has 500,000 message in their INBOX there are things that are definitely going to be slower (sorting, threading, etc) than if they have 100 message in their INBOX, saying that this is irrelevant tells me they probably haven't tested it to such extremes.

Yes, they can push a lot of this off to postgres, and appropriate indexing can greatly speed up searching and sorting, but it comes at a cost of slowing down adding or deleting messages (not to mention that it could require a lot of different indexes, many for single bit flags, so this can take a significant amount of storage, and therefor I/O to access)