Comment 1 for bug 307718

This is fine.

GTK loads the list of 80 items, only for the selected products. It is also smart in the way, it loads only fields that were not in the list view.

Loading one or 80 items is nearly the same time for postgresql (which is the bottelneck of the ERP) as it is the same number of queries. It allows to cache the data and work in cache when you do Next, Previous. The result is much less queries and server-client transactions. For complex fields (binaries, one2many, many2many) it loads only when you go on the record.

So, in my sense, GTK is much more faster than etiny, mainly because it is able to cache the selected records, in the client side. It allows you to do: next, next, next,... very fastly for a server-client application.

Please don't write bugs in uppercase, we set priority if we think it's important.