comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » point_lun is slow
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: point_lun is slow [message #17559 is a reply to message #17437] Fri, 29 October 1999 00:00 Go to previous messageGo to previous message
korpela is currently offline  korpela
Messages: 59
Registered: September 1993
Member
In article <381860B1.7145@gsfc.nasa.gov>,
George McCabe <george.mccabe@gsfc.nasa.gov> wrote:
> Struan Gray wrote:
>
>> simplest way to access this data be to use ASSOC to associate a huge
>> array of 2-byte variables with the file and then subscript it as
>> necessary to read in either frames or groups of individual pixels.
>
>
> Struan,
>
> ASSOC - certainly the simplest and also the fastest in cases where every
> element of the data is needed. but when for example only the
> [1538,395778,790018,... 434454018] location elements are needed from the
> file it is faster to point_lun to each. furthermore, the size of each
> associated read can affect the overall speed of a procedure. it's a
> better understanding of this subtlety that i am hoping for.

In this case memory mapping is definitely the way to go. Only accessed
pages get actually get read.

Eric

--
Eric Korpela | An object at rest can never be
korpela@ssl.berkeley.edu | stopped.
<a href="http://sag-www.ssl.berkeley.edu/~korpela">Click for home page.</a>
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Is there a way to keep axis text from scaling?
Next Topic: IDL 5.2.1 -- bug in filled contours?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 19:20:23 PDT 2025

Total time taken to generate the page: 0.00418 seconds