• Replies 5 replies
  • Subscribers 336 subscribers
  • Views 126 views
  • Users 0 members are here
Related

Best Practices in RAMP downloads. Output Sets

Tom Brown (Past Member)
$organization
I’m helping out over at Liberty Science Center for my current Residency.  They are in the process of moving onto RAMP from a self-hosted solution.  They have been accustomed to doing moderately sized Output sets.  (A few 10s of thousands of records.)  Saving as MS Excel to their hard drives.  Then edit the results from there.  On RAMP they are running into extreme slowness 10 or more minutes when they try to save the MS Excel output from a report to their local (on site) drive.  Is this RAMP normal?
 
The Scenario
1. Build a list with 10,000 constituents
2. Create an Output Set with 10-20 columns
3. Run Execute an output set  (This runs just fine)
4. Save and MS Excel with an onsite disk selected.  (Like the Local C Drive)
 
This take 10 or more minutes.  Often does not appear to complete, and user kills the application.
 
If I pick a drive that is local up on RAMP.  This save runs at normal speed.
 
Have you seen this on RAMP?
Do you have a workaround or best practices to tell users?
We believe that this happens with trying to save the results of any large Report across CITRIX.  
--Tom
Parents
  • $organization

    I would definitely try to save to RAMP first in a location that can be accessed by the file viewer/downloader app.  Filesystem access from RAMP is generally quite painfully slow.  Size is one issue, but any operation that involves large numbers of files, even small files, can be even slower.

Reply
  • $organization

    I would definitely try to save to RAMP first in a location that can be accessed by the file viewer/downloader app.  Filesystem access from RAMP is generally quite painfully slow.  Size is one issue, but any operation that involves large numbers of files, even small files, can be even slower.

Children