Hi Christian,
Yes, sorry, for some reason when I read it I didn't see the current_uri field and I thought it should be included so was asking you as much. Since it was there all along I have no idea how I missed it!
That was the index I'd thought about adding so it's good to see that you think it's a good index to use as well, maybe I should have just gone with my instinct two years ago when I first created the software.. ah well, I've just wasted some CPU time on thousands of sites! :)
That's very strange. Any rewrite rule that covers a URI removes that URI from the webserver error process unless the software itself generates a 404 header. If you could get in contact privately via this link with access details for one of the sites that had a problem I can take a look at the logs and htaccess file and see if I can find out why that is happening.
The vast majority of people using the module use URIs with no trailing slash. Actually, I'm not aware yet of anyone who does add a trailing slash, which is why I was thinking removing that functionality altogether (except for the root page of course as that is required by the HTTP spec) might be beneficial.. it would mean being able to use LIKE once more without a wildcard.
Ahh, that sounds very plausible indead. When Fawad posted his problem my thought was that maybe the connection the MySQL server was being dropped after each query and that the reconnection time overhead was responsible for the delays but I couldn't understand why that would be.
I didn't realise that MySQL by default caches the database table in memory, I imagined it would read it from disk and then cache a table as it was used, so all operations would always take place in a similar fashion. It's good to learn I got that wrong, so I won't make the same mistake again!
I'm well aware of that.. and of the exact reasons you wrote about.. I had been under the mistaken impression though that the previous VPS/shared server used was performing with site pages loading instantly and therefore that pages taking 16 seconds was a slowdown of possibly 16-100 times, which of course is a factor too big even for the difference between a cheap dedicated server and a VPS/shared server which had access for the necessary time to top rate hardware. Anyway.. that's all historical information for us now! :)
That certainly sounds like it!
Thanks for the nice comments.. hopefully with the addition of the index and the change to focussing on LIKE in the next version you might not consider the software to be "bad at database lookups" and only for tiny stores anymore? ;)
Yeah, small rather than tiny. Tiny is our store, it has 7 products! :)
As I was saying yesterday, I really have learnt something useful here.. I never thought a simple regular expression would be so inefficient.. whenever I changed the LIKE to REGEXP (a year or so back I think) I didn't see any noticeable change on my test server and heard nothing bad from anyone else so I thought that the MySQL developers must have optimised the software well enough for simple expressions (as I know in general regular expressions should be used as a last resort due the speed penalty imposed by the use of the reg exp engine), obviously that's not remotely true! Doubt Ill ever use a REGEXP in SQL again if I can avoid it! :)
I've just opened my New Riders MySQL book for the first time in about 5 years.. I think it's probably a good idea for me to create a test URI mapping database table of about 30000 records (or any amount that won't fit/be cached in memory) and try out a few options to see which is fastest.. I'll try to get time to do that later in the week and will include the quickest/most efficient index structure overall in a new version of the software.
Thanks for taking the time to provide your feedback, it's greatly appreciated.
All the best..
Conor
ceon
I am posting this in an honest effort to help the poster...
These are NOT for SEO, they are useful for usability. In fact, the issue of comparative load speed negates even that as speed is for SEO.I'm not here to critisize your hard work. No doubt you have already done a very good job to help people for their SEOs issues.
Issues remaining is still in part your webhost, as these parse times are somewhat slow.I must say "sorry" but you also try to understand that all three servers (shared, VPS, and dedicated) can't be misconfigured at once.
PageSpeed score 66/100Parse Time: 1.083 - Number of Queries: 322 - Query Time: 0.25248613789368
Still to be corrected for improvement:
1. 105 Errors, 10 warning(s)
2. Image optimization - This one for example (Header_down.jpg) is 975.99kb, and is loading but does not appear in the loaded page
3. Coded links within your pages to non www pages causing additional host lookups
4. Loading 7 individual stylesheets
5. Sloppy CSS which results in very large file sizes, optimize these
6. Unoptimized JS (categories_css.js), which is also loading in the body rather that the <head>
While rewriting your urls does not help you rank, speed does.... and it is a growing part of Google algorithm.
~Melanie
PRO-Webs, Inc. :: Recent Zen Cart Projects :: Zen Cart SEO – 12 Steps to Success
**I answer questions in the forum, private messages are NOT answered. You are welcome to contact us via our website for professional engagements.
Regarding trailing slashes and their omission from URLs:
The trailing slash denotes a folder URL, one that will serve the folder index.
URLs for HTML pages do not have a trailing slash, and do not have to have an extension.
This is mentioned in the HTTP specs.
For "pages" it is also common for "with slash" URL requests to be redirected to "without slash" to prevent Duplicate Content issues.
For "folders", the server's own inbuilt default redirect acts to add the slash on when a folder name is requested without the slash.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Thank you so much for the comments given by all the experts here.
Today, i have come across a new problem related with either 'cache' or session'. As soon as i go for checkout after adding product in the cart, the message "Your shopping cart is empty" displays.
I have gone through different threads related with this issue but none of them helped me out.
Note:
I have already applied 'fix_cache_key.php' and it has updated the path in "Session Directory". Further if i apply, it shows "No change requires".
Please suggest me what else i can do to resolve this issue.
mprough, you have given wonderful analysis. I'll definitely going to fix the warnings and errors.
Hi Fawad,
How are you?
I sent you a PM about checking out various options for quicker database access with your URI mappings but haven't heard from you.. just checking if you got it okay? (I know I don't always get the notifications for various reasons so thought it best to check).
All the best..
Conor
ceon
I'm really sorry for late response. Actually i missed that PM. Can you please send that again, if you don't mind?
Bookmarks