Re: Filling a hash view
Pat Thoyts <[email protected]> Fri, 5 Mar 2010 00:05:32 +0000
| Newsgroups | gmane.comp.db.metakit |
|---|---|
| Message-ID | <[email protected]> |
On 4 March 2010 19:37, Marcin Krol <[email protected]> wrote: > Hello everyone, > > I'm "testdriving" metakit 4 py now, and I have a little trouble with hashed > view: when the number of keys in view starts exceeding 2000, filling up a > hash view becomes extremely slow. When a view has a lot of rows you can fix the performance issues using a blocked view. This is another wrapper around the view but it keeps the performance in check. I've no idea about python but in C++ c4_View v = rFiles(view[nInode]); m_vFiles = v.Blocked().Ordered(); When defining the layout you add a _B[] around the view description. The performance issue is that metakit is column oriented. So when you add a new row it moves whole columns around. By breaking this into blocks it restricts the size of the columns. I use this kind of view to manage 200 000 rows per view quite handily. Pat. -- You received this message because you are subscribed to the "metakit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/metakit?hl=en