dhis2-users team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

Well this would just solve the problem for one report.  Where there is one
there will be more ...


On 16 September 2013 10:22, Jason Pickering <jason.p.pickering@xxxxxxxxx>wrote:

> Why not just  use a new location ? Is it too easy or am I just not getting
> it or something similar/more elegant?
>
> location ~ /api/reports/<UID OF REPORT GOES HERE>/* {
>
>       proxy_redirect    off;
>       proxy_set_header  Host               $host;
>       proxy_set_header  X-Real-IP          $remote_addr;
>       proxy_set_header  X-Forwarded-For    $proxy_add_x_forwarded_for;
>       proxy_set_header  X-Forwarded-Proto  http;
>       #proxy_cache       dhis; DONT CACHE!
>
> }
>
> Regards,
> Jason
>
>
>
> On Mon, Sep 16, 2013 at 11:07 AM, Bob Jolliffe <bobjolliffe@xxxxxxxxx>wrote:
>
>> I think the sendfile feature has to do with whether nginx does
>> asynchronous i/o using the sendfile() function in linux kernel, so I doubt
>> turning it on or off is going to help us here.
>>
>> Agree with Jason that pulling stuff back out of the cache is a hack but
>> trying hard to think of a workaround.
>>
>> Lars suggestion is interesting.  Probably the proper eventual solution is
>> to have a checkbox on the report design ("Don't Cache").  Mind you once its
>> cached once you are stuck till its expired again.
>>
>> Randy I can disable caching on nginx temporarily and we can monitor how
>> the performance is.  You will still have browser cache and your postgres is
>> quite well provisioned so it might be ok.
>>
>> Bob
>>
>> On 15 September 2013 19:00, Saptarshi Purkayastha <sunbiz@xxxxxxxxx>wrote:
>>
>>> is the following mentioned in nginx.conf
>>> sendfile=on;
>>> This will make the file sending cached by nginx.
>>> If you turn this off... nginx will send the generated file to user,
>>> instead of the one that's cached
>>>
>>> ---
>>> Regards,
>>> Saptarshi PURKAYASTHA
>>> ------------------------------
>>> Date: Sun, 15 Sep 2013 19:56:39 +0200
>>> From: larshelge@xxxxxxxxx
>>> To: jason.p.pickering@xxxxxxxxx
>>> CC: dhis2-users@xxxxxxxxxxxxxxxxxxx
>>> Subject: Re: [Dhis2-users] Standard iReports cache problem
>>>
>>>
>>> Of course that doesn't fix the problem with the constantly updated
>>> report (unless you create a Resource and points it to that Report including
>>> that query param). If this is a special case for just one report then I
>>> guess Jason's suggestion on a special nginx location would be feasible. We
>>> could implement a system feature but that will take longer.
>>>
>>> _______________________________________________ Mailing list:
>>> https://launchpad.net/~dhis2-users Post to :
>>> dhis2-users@xxxxxxxxxxxxxxxxxxx Unsubscribe :
>>> https://launchpad.net/~dhis2-users More help :
>>> https://help.launchpad.net/ListHelp
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>