Re: [Typo correction] Is it good for performance to put rows that are of different types but are always queried together in the same table partition?

(which is effectively what will happen if you put them into the same table and use query-1table-b), as each node will only need to merge cells/results once. It may not be twice as fast, but it’ll be fast enough to make it worthwhile. On 1/8/16, 12:13 AM, "Bamoqi" mail

[Typo correction] Is it good for performance to put rows that are of different types but are always queried together in the same table partition?

[Correction of the original message which contains typos in code.] Is it good for performance to put rows that are of different types but are always queried together in the same table partition? My consideration is that whether doing so will result in better memory/disk cache locality. Supp

Is it good for performance to put rows that are of different types but are always queried together in the same table partition?

My consideration is that whether doing so will result in better memory/disk cache locality. Suppose I need to query for 2 different types of rows for a frequent user request, I can use 2 tables or 1 table: 2 tables: create table t1( partitionkey int primary key, col1 int, col2 int,