topic Reduce in server or in Section Access in Water Cooler

Reduce in server or in Section Access

Mon, 09 Apr 2012 15:46:56 GMT

I have an application that is divided by sector (purchases, sales, inventory). I divide into different files by using the tab "Reduce" and grant access using the tab Distribute > Loop field in document.

The resulting files are small, but how they stay in memory? This is a better approach than reduction in Section Access?

Somebody know?

Thanks.

Reduce in server or in Section Access

Miguel_Angel_Baeyens — Mon, 09 Apr 2012 15:57:03 GMT

Hi Joao Paulo,

It will depend widely on how the document has been built and how many resources does it use when in memory. Generally speaking, many small documents with little timeout values will perform better than one huge document accessed concurrently by a lot of users with higher timeouts. Hence, your approach seems all right to me, but don't take my word for it, and test it using several users and different sizes of documents.

Are your users going to make always the same queries, so they are going to be cached quickly and so returned faster (one huge doc) or are they rather going to make very different selections on many different fields and sets of information (many small docs)? How long does it take for them the use of the QlikView app?

Hope that makes sense.

Miguel

Reduce in server or in Section Access

Mon, 09 Apr 2012 19:09:10 GMT

Miguel,

It makes sense.
I will continue evaluating. If you find any information relavante'll post.

If you find out if the documents in memory are unified, please let us know.

Thanks,