Smalyshev added a comment.

@BBlack, thanks for raising these issues, this is definitely something we 
should address.

> If it were sent un-chunked with a Content-Length, the varnish would have a 
> chance at caching it.

It may be how Blazegraph sends it. But maybe we coould un-chunk it on the way 
(nginx? inside blazegraph?).

> I don't think we really want client control of object expiration (at least, 
> not "varnish cache object expiration"),

Yes, but I was thinking more of a scenario where Varnish has an object in 
cache, but may decide to still go to backend, or serve from cache, depending on 
incoming parameters. Is this possible? In general, is it possible in Varnish to 
decouple the lifetime of object in cache from the decision of whether to serve 
the object from cache or from backend? E.g. so that if the client is OK with 
being served "old" object, it will be served, but if not, then the object will 
be served only if it's relatively "fresh", even though it can be retained for 
longer for less demanding clients. Not sure if we'd need it that complex, but 
would be nice to know whether it's possible.

> You might initially post the complex SPARQL template and save it as fooquery

I am not sure we want to go into explicitly saving named query, as I am not 
sure it can scale. That said, I didn't explore saved queries too deep yet, so 
I'll keep it in mind and try to look into it ASAP. But so far I think caching 
is better alternative and also much simpler.

> The plans in this ticket sound nothing like that, and cache_misc probably 
> isn't an appropriate home for a complex query services

Correct. We probably need to consider this.


TASK DETAIL
  https://phabricator.wikimedia.org/T126730

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Smalyshev
Cc: Gehel, BBlack, GWicke, Bene, Ricordisamoa, daniel, Lydia_Pintscher, 
Smalyshev, Jonas, Christopher, Yurik, hoo, Aklapper, aude, debt, Izno, 
Luke081515, jkroll, Wikidata-bugs, Jdouglas, Deskana, Manybubbles, Mbch331, 
Jay8g, Ltrlg



_______________________________________________
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to