-
Re: Ideas on Reloading Same app in two streams
Bill Markham Mar 7, 2017 10:09 AM (in response to Guruprem Saginadham )Maybe binary load the second app from the first.
-
Re: Ideas on Reloading Same app in two streams
Shubham Singh Mar 7, 2017 11:19 AM (in response to Guruprem Saginadham )It shoud not matter if your reloading same app twice. You should use a proper 3 layer architechture so that your published UI app should only take a few seconds to maximum two minutes for reloading. To do that move all your calculations to a transform layer and UI should only contain LOAD * statements.
-
Re: Ideas on Reloading Same app in two streams
Bill Markham Mar 7, 2017 11:38 AM (in response to Shubham Singh )..maybe not always a Load *, best to only load the fields from QVD that are needed. This will de-optimise the QVD load.
-
Re: Ideas on Reloading Same app in two streams
Shubham Singh Mar 7, 2017 12:02 PM (in response to Bill Markham )Why store those fields in QVD if you don't need them in UI. Drop those unnecessary fields before storing QVD. This will reduce size of QVD.
-
Re: Ideas on Reloading Same app in two streams
Bill Markham Mar 7, 2017 12:55 PM (in response to Shubham Singh )QVD's can be used as data sources for multiple dashboard apps and some app[s] may need different fields from the QVD's than other app[s] need.
But yup, if no apps need certain fields from the QVD - then as you suggest best not store in the QVD fields that nothing uses.
-
-
-
-
Re: Ideas on Reloading Same app in two streams
Guruprem Saginadham Mar 7, 2017 11:45 AM (in response to Guruprem Saginadham )Thanks. I do follow scripting best practices. Now I found that question it self in correct because when there are two apps they will be loaded twice all we can do is load only from QVDs. Thanks let me close this thread.