Because in-memory databases do not use I/O, you need not consider device I/O characteristics (for example, the speed of the I/O device) when organizing physical data placement. You need not consider issues like locating frequently accessed index pages on fast devices, or pages for other infrequently utilized objects (for example, text and image pages) on slower devices. However, because in-memory databases remove other bottlenecks caused by disk I/O, other bottlenecks such as spinlock and latch contention may be high.
Consider the following when you organize physical data for in-memory devices:
To reduce latch contention, use separate data and log devices (that is, do not configure in-memory databases for mixed log and data).
To control log space consumption, use separate log devices.
To restrict object space usage, organize devices in segments.
To reduce contention for page allocation, use segments bound to different devices.
