Hi,
At what point does it begin to affect performance with the number of
redirects and rewrites being used on a website? Have there been any
performance studies on this?
We have a website (linuxsecurity.com) that's been around for decades,
through many migrations, and have collected many (~10k) redirects along
the way.
We've also gone through a Joomla migration from the old
/content/view/33/45 style links to the SEF/title alias format, and have
a script that translates those dynamically as requested.
Of course it depends on server load and other factors, but when does it
become a point where searching through thousands of links that Apache
has stored in memory results in some significant additional delay?
Are there other methods of doing these redirects? Would implementing
them in Joomla directly make any difference, or only add another layer
of abstraction?
Here's one example of a rewrite we're currently using:
RewriteRule
^/features/features/verifying-linux-server-security-what-every-admin-needs-to-know$
/features/features/verifying-linux-server-security [L,R=301]
RewriteRule
^/advisories/fedora/fedora-25-rubygem-rmagick-security-update$
/advisories/fedora/fedora-25-rubygem-rmagick-security-update-15-25-00-217101
[L,R=301]
Also, is there a way to trace a specific redirect? I've somehow created
a redirect loop with one of our articles, but enabling tracing on the
whole site will create a significant amount of data that makes it very
difficult to focus on just the one I'm interested in.
LogLevel warn ssl:error auth_digest:error socache_shmcb:warn
mpm_worker:warn fcgid:info cache_disk:debug log_config:debug rewrite:trace3
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
At what point does it begin to affect performance with the number of
redirects and rewrites being used on a website? Have there been any
performance studies on this?
We have a website (linuxsecurity.com) that's been around for decades,
through many migrations, and have collected many (~10k) redirects along
the way.
We've also gone through a Joomla migration from the old
/content/view/33/45 style links to the SEF/title alias format, and have
a script that translates those dynamically as requested.
Of course it depends on server load and other factors, but when does it
become a point where searching through thousands of links that Apache
has stored in memory results in some significant additional delay?
Are there other methods of doing these redirects? Would implementing
them in Joomla directly make any difference, or only add another layer
of abstraction?
Here's one example of a rewrite we're currently using:
RewriteRule
^/features/features/verifying-linux-server-security-what-every-admin-needs-to-know$
/features/features/verifying-linux-server-security [L,R=301]
RewriteRule
^/advisories/fedora/fedora-25-rubygem-rmagick-security-update$
/advisories/fedora/fedora-25-rubygem-rmagick-security-update-15-25-00-217101
[L,R=301]
Also, is there a way to trace a specific redirect? I've somehow created
a redirect loop with one of our articles, but enabling tracing on the
whole site will create a significant amount of data that makes it very
difficult to focus on just the one I'm interested in.
LogLevel warn ssl:error auth_digest:error socache_shmcb:warn
mpm_worker:warn fcgid:info cache_disk:debug log_config:debug rewrite:trace3
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org