[webservices] default in bulkdataselect
Chad Trabant
chad at iris.washington.edu
Wed Aug 29 08:51:54 PDT 2012
Hi,
Yes, the default values are as you guessed. By default there is no limitation based on segment length, the documentation has been updated.
Regarding ws-dataselect versus ws-bulkdataselect performance for large miniSEED requests: early tests indicated there is a performance difference for the user, but I haven't tested for a while and it's dependent on a number of factors. Also, there is a difference for the DMC internally. In short, if you just want raw miniSEED data ws-bulkdataselect is the preferred interface.
A bit more explanation:
For the ws-dataselect requests the data are placed into an internal cache for use, for example, by other services. The user needs to wait for the data to be extracted and cached. For ws-bulkdataselect requests the data are not cached, but are effectively streamed back to the user from the storage system directly. The extraction and caching can be really fast compared to the network connection to the user, so this difference is not always obvious but it would likely add up. For large requests of raw data ws-bulkdataselect is preferred as it uses fewer resources at the DMC.
Chad
On Aug 29, 2012, at 5:40 AM, Philip Crotwell wrote:
> Hi
>
> What are the default values for minimumlength and longestonly? I am
> guessing 0 and false, but the docs don't say.
> http://www.iris.edu/ws/bulkdataselect/
>
> Also, have you found a performance increase with bulkdataselect over
> dataselect for large miniseed downloads?
>
> thanks
> Philip
> _______________________________________________
> webservices mailing list
> webservices at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/webservices
More information about the webservices
mailing list