[NumPy-Tickets] [NumPy] #2080: Issue with memory mapping large files

NumPy Trac numpy-tickets@scipy....
Tue Mar 13 18:34:53 CDT 2012


#2080: Issue with memory mapping large files
------------------------+---------------------------------------------------
 Reporter:  for_usenet  |       Owner:  somebody   
     Type:  defect      |      Status:  new        
 Priority:  normal      |   Milestone:  Unscheduled
Component:  numpy.core  |     Version:  1.6.1      
 Keywords:  mmap        |  
------------------------+---------------------------------------------------

Comment(by for_usenet):

 Replying to [comment:1 charris]:
 > Curious. I can memmap a 12 GB file:
 >
 > {{{
 > In [5]: f = np.memmap ('testfile', mode = 'r', dtype = np.int16)
 >
 > In [6]: f.shape
 > Out[6]: (6144000000,)
 > }}}
 >
 > Just to make sure you are running 64 bit python, what does
 >
 > {{{
 > charris@f16 ~$ file `which python`
 > /usr/bin/python: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
 dynamically linked (uses shared libs), for GNU/Linux 2.6.32, stripped
 >
 > }}}
 >
 > show?

 On my OS X system, that gives:

         19:27:29 747% file `which python`
         /usr/bin/python: Mach-O universal binary with 3 architectures
         /usr/bin/python (for architecture x86_64):      Mach-O 64-bit
 executable x86_64
         /usr/bin/python (for architecture i386):           Mach-O
 executable i386
         /usr/bin/python (for architecture ppc7400):    Mach-O executable
 ppc

 and on openSUSE,

         :~> file `which python`
         /usr/bin/python: symbolic link to `python2.7'
         :~> file `which python2.7`
         /usr/bin/python2.7: ELF 64-bit LSB executable, x86-64, version 1
 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.4,
 stripped

-- 
Ticket URL: <http://projects.scipy.org/numpy/ticket/2080#comment:2>
NumPy <http://projects.scipy.org/numpy>
My example project


More information about the NumPy-Tickets mailing list