>
> As you can see, tuple accesses are independent of data size, > as the data already resides on the process heap. With ets, > there is always copying, so as the object size increases, so > does the cost of a lookup. Hm... might one suspect that the real villain is the copying of data into the asking process, rather than the ets lookup in itself? -- Thomas