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?

16, 12:13 AM, "Bamoqi" <bam...@gmail.com <mailto:bam...@gmail.com>> wrote: >[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 toget

[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.

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