Difference between revisions of "Fastpath"
(New page: On the AOLserver list, Tom Jacksov wrote The purpose of the API is to return a static file, not one which changes in under a second. It is not a bug to not support code which is guarantee...) |
m |
||
| Line 1: | Line 1: | ||
| − | On the AOLserver list, Tom | + | On the AOLserver list, Tom Jackson wrote |
The purpose of the API is to return a static file, not one which changes in under a second. It is not a bug to not support code which is guaranteed to be slower than common alternatives. | The purpose of the API is to return a static file, not one which changes in under a second. It is not a bug to not support code which is guaranteed to be slower than common alternatives. | ||
Revision as of 13:17, 19 August 2008
On the AOLserver list, Tom Jackson wrote
The purpose of the API is to return a static file, not one which changes in under a second. It is not a bug to not support code which is guaranteed to be slower than common alternatives.
Fastpath is designed to support return of smallish static content. It isn't some ancient way of speeding up stuff that was slow, it was for speeding up stuff that was already fast but was easy to make even faster.
If you want to avoid use of fastpath, just set the configuration lower than your dynamic content:
#
# Fastpath
#
ns_section "ns/server/${server}/fastpath"
ns_param cache [set cache 10] ;# max entries ??
ns_param cachemaxsize [set cachemaxsize [expr 5 * 1024 * 1024]]
ns_param cachemaxentry [expr round(floor($cachemaxsize/$cache))]
Or, if the dynamic content is very small, or customized, don't write it to a file in the first place. In general you are probably doing something wrong if you write small content to a file and immediately delete it. You are also likely doing something wrong if you are caching large files.
