count(*) avg(length(oxstdurl)) max(length(oxstdurl))
avg(length(oxseourl)) max(length(oxseourl))
173199 116.8874 404 74.6858
325
173199
Kindest regards
Tobias Merkl
Software-Entwicklung
*************************************
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel (09 11) 2 55 66 - 25
Fax (09 11) 2 55 66 - 29
eMail [email protected]
Web www.shoptimax.de
*************************************
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*************************************
-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]] Im Auftrag von Šarunas
Valaškevicius
Gesendet: Mittwoch, 27. April 2011 13:06
An: [email protected]
Betreff: Re: [oxid-dev-general] oxseo fullscan
Hi,
we are currently fixing this issue,
https://bugs.oxid-esales.com/view.php?id=2740 .
The solution to change oxstdurl and oxseourl fields to varchar(2048)
currently sounds the best.
Also, to select good indexing length we would need feedback about usual
lengths of these data in real shops.
Please help us by gathering some statistical data about these data in
your shop database.
Could you please run the following query and send us the results? (just
post the results here in the dev general)
SELECT oxstdurl,oxseourl FROM `oxseo` PROCEDURE ANALYSE(1,1);
together with data count returned by
SELECT count(*) FROM oxseo;
if it wouldn't work (e.g. some mysql clients automatically append limit
clause after procedure), you could also use simple sql such as:
select count(*), avg(length(oxstdurl)), max(length(oxstdurl)),
avg(length(oxseourl)), max(length(oxseourl)) from oxseo;
Note, that on huge databases these selects will increase load.
Especially if your database is already under heavy load,
it would be best to run it on a separate db clone or at least on more
idle hours.
Regards,
Sarunas
On Tue, 2011-04-26 at 16:01 +0200, anzido GmbH wrote:
> Hi,
>
>
> > I think it would be useful, to change the oxstdurl to an varchar-type and
> > impose this column with an index?
>
> It's not only "useful" - it's absolutely essential if you have a big shop
> with much traffic!
> Also you should take care that searching for seo urls is done only if the std
> url CAN HAVE any seo url. For example if the std url looks like:
> index.php?force_sid= .... OR index.php?stoken=.... OR index.php?....
> cl=search and so on - there is NO seo url and searching for it is absolutely
> needless and a waste of ressources.
>
> On one of our bigger projects we reduced the total number of sql queries by
> nearly 20%!
>
>
> Beste Grüße aus Dortmund!
> Andreas Ziethen | Geschäftsführung
>
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
