[ 
https://issues.apache.org/jira/browse/TS-4326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356314#comment-15356314
 ] 

Leif Hedstrom commented on TS-4326:
-----------------------------------

If we do this, we should remove and deprecate the healthcheck plugin. A few 
observation from the work on the old plugin, and the ACME plugin:

1) The usage of inotify was probably premature optimization, I don't think this 
is needed.

2) More importantly, the caching in memory was likely also premature 
optimizations. I benchmarked the ACME plugin, which also serves static files, 
but somewhat differently (it's a global txn intercept). But even doing a stat() 
/ open() on the file on each access was very, very fast.

3) We should make sure this new plugin is a remap plugin, usage like
{code}
map http://example.com/static http://doesntmatter.com @plugin=static_files.so 
@pparam=--docroot=/var/html/static_files
{code}

4) It'd be useful to have a basic notion of ".htaccess" features to put into 
each directory. I'd be ok with having those as pparam= options too (or both).

5) I think though that a requirement would be to allow for a MIME types 
configuration file of some sort. This is to assure that we serve the static 
files with appropriate Content-Type: header.

> Make a generic file serving plugin (server intercept)
> -----------------------------------------------------
>
>                 Key: TS-4326
>                 URL: https://issues.apache.org/jira/browse/TS-4326
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Plugins
>            Reporter: Leif Hedstrom
>            Assignee: Jari Alhonen
>             Fix For: 7.0.0
>
>
> I think this can also (likely) replace e.g. the health checks plugins. I did 
> some benchmarks, even doing an open() / read() sequence on every request can 
> still serve a lot of traffic.
> We should write this as a remap plugin, with server intercepts, very similar 
> to the generator plugin.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to