How much byte of memory does LASR server take to store a length 1 character data and lenght 8 numeric data ?
@alexal wrote:
Each column in the LASR server is padded to an 8 byte boundary. If the character variable you are adding is not a multiple of 8 bytes, the variable will be padded to an 8-byte boundary.
Didn't know that. Now that can blow up a dataset quite nicely (if it contains lots of y/n type variables).
There will always be an overhead for metadata, and artifacts of the page-wise organisation of datasets. But a 1-character field needs one byte, and the larger the dataset (in terms of observations), the smaller the overhead.
Each column in the LASR server is padded to an 8 byte boundary. If the character variable you are adding is not a multiple of 8 bytes, the variable will be padded to an 8-byte boundary.
@alexal wrote:
Each column in the LASR server is padded to an 8 byte boundary. If the character variable you are adding is not a multiple of 8 bytes, the variable will be padded to an 8-byte boundary.
Didn't know that. Now that can blow up a dataset quite nicely (if it contains lots of y/n type variables).
Is there anything like 8 byte padding in case of numeric columns ?
A numeric column of length 8 takes up 8 bytes of memory? Please correct me if I am wrong.
Correct. Numeric columns use 8 bytes of storage by default so no padding is done for these. If the LASR load table contains shortened numerical columns I presume padded would be done for these too.
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!
See how to use one filter for multiple data sources by mapping your data from SAS’ Alexandria McCall.
Find more tutorials on the SAS Users YouTube channel.