Will this optimization help on virtualized machines like Xen? Or does all memory appear to be the same? On an EC2 m1.xlarge: $ numactl --hardware available:

Will this optimization help on virtualized machines like Xen? Or does all memory appear to be the same? On an EC2 m1.xlarge: $ numactl --hardware available: 1 nodes (0) libnuma: Warning: /sys not mounted or invalid. Assuming one node: No such file or directory node 0 cpus: node 0 size: <not available> node 0 free: <not available> libnuma: Warning: Cannot parse distance information in sysfs: No such file or directory