[erlang-questions] Guidance to a cache mechanism

Maruthavanan Subbarayan <>
Wed Oct 31 06:55:08 CET 2012


Hi Richard,
I thought of keeping the time stamp as the key in the ets table and maintain that in state when a timeout event occurs. I hope this would help me to delete the entries in ets table with less burden.
Thanks,Marutha
> Subject: Re: [erlang-questions] Guidance to a cache mechanism
> From: 
> Date: Wed, 31 Oct 2012 11:18:11 +1300
> CC: 
> To: 
> 
> 
> On 31/10/2012, at 12:08 AM, Maruthavanan Subbarayan wrote:
> - messages contain up to 200 bytes
> - "maybe 500+" messages per second
> - maximum expiry 60 minutes
> for a total of 360,000,000 bytes.
> 
> I'm wondering whether you actually need ETS at all.
> 
> + Something gives your program a message.
> + Time tells your program when to delete a message.
> ? How is your program asked to give a message back?
>   A message is presumably going to be requested via
>   some sort of key, which is presumably _not_ going
>   to be the timestamp when it arrived, so you will
>   want some kind of index to find the right message, no?
> 
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121031/879c2203/attachment.html>


More information about the erlang-questions mailing list