28 Seconds! I just timed this myself, and the login process took 28.6 seconds! (28662ms) I have a 22mb internet connection - the fastest available to consumers in the UK, and I know logging in has been slower before. lol! I hope my site doesn't turn out like this... I'm completely hacking the code so I don't have to use the plugin architecture at all - I'm hard coding everything.
Hi! What's the colour of your clock? What a nightmare... I need to buy a very precise GMT clock for my computer? Holy ghost, we seem to have extremes of problems and expertise here! Mind you sharing your expertise on your hardcoding experience? What did you do to get out of plugins.inc.php & db.inc.php?
I used a simple Firefox addon to do the timing - I didn't want human error! RE: Hard-coding The aMember code is very well written, but poorly designed - if that makes sense! This means that it isn't too difficult to 'copy' and re-write the functions in the actual plugin files and trigger them on pages like signup.php and profile.php where needed - this gives you much more flexibility and speeds everything up a lot. A lot of the functions are wrapped in classes, but if you know a bit of php you can re-write the functions so they can run independently wherever you want them to go. I'm only integrating aMember with PHPList - but I've bought other plugins too and have looked at the code - doing the same with your plugins would be exactly the same. The database interface doesn't run as a plugin - it's just a class (called 'db'). I don't have the real code for this (zend encoded), but I've requested the original file from aMember support, which they should provide to me (they've given it to users before). Once I've got the actual code I'll be able to use my own optimised/customised functions for all functionality, rather than having to create my own functions dotted all over the place.
Hello joe_asto2! Well, thats a complete new strategiy, well thought. But that would not help many here as it an entirely different approach. Thanks for sharing...
This issue seems to be getting worse...Alex, your site login is VERY slow. I usually hit the login, then go make a sandwich... Any news on an update fix?
Hi! I seem to be getting very curious on your issue... 1. Are you on a dedicated real server? 2. Can you disable the error, access etc routines? 3. Disable some extra plugins that you do not use. 4. Work with the mysql temporary table cache. How many are created on the disk? 5. How many users record do you have? 6. What about the RAM available?
Afew months ago Alex mentioned: Just wondering if a new version is due out sometime soon. It's been 6 month + since the last release...and about time to renew my support subscription. I hope Alex remembers the "auto fill" standards I sent a few month back, since the first name / last name does not properly autofill on signup. (first AND last name are placed in the first name field, last name remains blank) -------------------- Draj: I was referring to THIS site >AMEMBER.com<, it is the site that was slow. Mine is also slow. So I figure it is a problem common to both sites, ie: version 3.0.8 Alex seems to have fixed the login delay now...but on his site, not mine. I am waiting for the new revision. to answer your previous questions: 1. Are you on a dedicated real server? DEDICATED DUAL CORE - VERY Lightly Loaded 2. Can you disable the error, access etc routines? - no error displayed, only delay on amember.com and logging into my site. 3. Disable some extra plugins that you do not use. No extra plugins used. 4. Work with the mysql temporary table cache. How many are created on the disk? ???????? 5. How many users record do you have? over 12,000 6. What about the RAM available? 1Gb These questions will all be moot if Alex releases a new rev. since he has obviously fixed the delay problem on amember.com
Hoi, If Alex got angry in using anathor software he was using, then he would have removed the integration due to which amember would have got faster. It was the same software that made me very angry too. But that login problem did not have anything to do ith any logical aspects of aMember. Apart from the amember site: I am shocked by your description of the hardware etc. you are describing, if amember is slow due to amember programming. It could be because of that, however you MUST fine tune mysql.conf. Mind you, 12,000 users is nothing. Important is how many concorrent connections you have, whether they are persistant ones, or if the data is swaping, temporary tables created, table cache, etc. Here you need to look in to those things..