in_memory workspace best practices?

Discussion created by curtvprice Champion on Mar 29, 2013
Latest reply on Apr 3, 2013 by kimo
This is a discussion post.

I've been very conservative with my use of the in_memory workspace, mostly using it to set up tables and add and delete fields quickly and conveniently. However at 10.1, we can now even write rasters there, and the questions come up:

- Is the in_memory workspace stuck within the application space, ie does it have to fit in ArcMap's x32 space on an x64 machine?
- Is there a way to estimate "used" or "available" space in the in_memory workspace?
- Has the Esri GP team or users done any exploratory analysis on the conditions which cause the in_memory workspace to cause system thrashing or other problems?
- Has anyone benchmarked performance of in_memory vs and SSD? I would think the SSD woudl be slower as you would need to push data through the bus, in_memory would be "on-board" so to speak.

Given this is a YMMV kind of thing - people's systems and work habits are different - but it would be nice to have some best-practices based on user experience.

Discuss among yourselves.