On Tue, Mar 18, 2014 at 2:55 PM, Saminda Wijeratne <[email protected]>wrote:
> For performance issues a gateway should only request a subset of data of > an experiment from Airavata server to compile a summary view of the > experiment to the scientist. Based on my current experience I feel the > following data is required to compile a general summary. > > - Exp ID/Name > - Status > - Project > - Owner/Creation time > +1, We can show minimum data and give detailed view on-demand. But I think we need to support experiment search based on some criteria and develop an index for each search criteria, because if I ran jobs for 6 months and I would never want to get all my experiments, even thought we make it super fast will minimum data. ex: I want to search the experiments I ran last week, or with some text base search. We can use the above solution Saminda suggested in searching too. Lahiru > > We have seeing a direct relationship between the number of experiment data > records and the turnaround time. Thus we may need some paging when > requesting the experiment data. > > wdyt? Your thoughts are welcome. > > (Using JIRA [1] to track the status of this task) > > A detailed discussion on the topic is on the Architecture mailing list [2]. > > Regards, > Saminda > > 1. https://issues.apache.org/jira/browse/AIRAVATA-995 > 2. > http://www.mail-archive.com/[email protected]/msg00080.html > -- System Analyst Programmer PTI Lab Indiana University
