Jump to content

peal

Members
  • Posts

    31
  • Joined

  • Last visited

Profile Information

  • First Name
    Pavel
  • Last Name
    Knezek

Recent Profile Visitors

228 profile views

peal's Achievements

Newbie

Newbie (1/14)

1

Reputation

2

Community Answers

  1. Actually that's not a problem - site is working without errors. The reason why I am asking is that we have currently php 5.2 with APC and nothing else. While upgrading server, we would like to be prepared and take it as the opportunity to get maximum of it. For now we are sure APC can;t be used with php 5.6. APCu seems to be a replacement but some claim that inbuilt opcache is enough. The same with mod_pagespeed - for some must have, for others buggy module which should be avoided. I would love to see some opinions what can be used alltogether.
  2. Hello, I am a little bit confused (ok, more than little) about all the caching systems used around. We are going to upgrade our server and prestashop as well so I would like to sort out few things... Server is nginx with php 5.6 installed. PS version would be latest probably. Now, what are the possibilities to speed it up? I read it is good to use APCu, memchached and pagespeed. Is it possible to use them all without conflicts, or are they some alternatives and it's better to use just one (or some)? I have read pagespeed documentation and it seems to do lot's of impressive things. This one looks promising to me. Currently we were using APC but it's not supported in PHP 5.6 anymore, but there is APCu. I believe this cache system is used for caching compiled php files? And finaly memcached. I do not have any experience with it but I found several articles it's used very often as well. Could I ask you to clarify which one is ok to use on up to date server? Thank you very much for any related comments.
  3. Az priste budete mit opet problem, v prvni rade si opiste vsechny chybove hlasky, ktere uvidite. Lip se pak hleda pricina
  4. Podle tech grafu se problem tykal cloudu ve Francii, coz se vas opravdu netyka. Pricinu problemu bych hledal jinde.
  5. Zkusim to, snad vam nebudu vykladat nepravdy, vychazim z toho co vim a co mam odzkouseno. Prestashop je mozno pouzivat jako cloudove reseni, coz je relativne novinka a v podstate mate hosting s predinstalovanou prestou na jejich serverech. Ve vasem pripade mate ale zrejme klasickou instalaci, takze vsechna data jsou ulozena u vas (na serveru hostingu). Vse se tam take zpracovava, ke kontaktu se servery prestashopu podle me dochazi jen v backofficu v prehledu modulu, kde se kontroluje jestli neni k dispozici aktualizace. Takze nic, co by melo ovlivnit rychlost obchodu. Jestli jste zazil nejake problemy s rychlosti, tak bych se vsadil ze slo nejspis o problem prave u hostingu, zvlast pokud mate sdileny hosting. Ve spicce muze mit vas shop k dispozici mene vykonu nez obvykle, coz se projevi zpomalenim. Jak jste vlastne dosel k tomu, ze byla chyba na presta serveru?
  6. 1. Neni potreba jeste doupravit kosik? Tam se take zobrazuji ceny. 2. Tak toto je urcite snazsi reseni, na to jsem zapomel
  7. 1) Jedine co me napada, je uprava templatu, ale muselo by se to predelat na spouste mist, coz by vedlo akorat tak ke zmateni, protoze tech mist je opravdu dost. Skutecne je nutne tam tuto hodnotu davat? V maloobchode je zvykem, ze pokud je uvedena jedna cena, je s dani, tak proc to dopisovat? Pripadne by melo stacit pridat tuto informaci do obchodnich podminek, nebo nekam na viditelne misto. 2) Reseni je jednoduche, staci na stitek v css aplikovat styl display: none;
  8. Pokud mate cloudovy prestashop, tak tam problem byt muze, pri instalaci na vlastni server ale k pripojeni na presta servery ani nedochazi.
  9. Podle mych zkusenosti opravdu pomaha spravne urcit problem, to znamena na ktere strance (homepage, kategorie, produkt...), zapnout na chvili debug a zkontrolovat mysql a moduly. Proste takova ta klasika. Co mi zatim nejvice zpomalovalo shop je toto: - bloky s novym/doporucovanym zbozim, hlavne dalsi zbozi v teto kategorii. nahrava to moc dat a pritom zbytecne, takze pokud mozno srusit, nebo aspon omezit jen na par kusu. - block layered, neboli filtry. to je kategorie sama o sobe, v soucasne dobe lepsi se tomu vyhnout uplne - zapnute cachovani v optimalizaci dole: mam zkusenost jen s apc, ale presta cachuje spatne a cache za par hodin fragmentuje na 100%, takze zacne zpomalovat. Lepsi je to v preste vypnout, ale samozrejme na serveru mit apc zaple. - zbytecne velke obrazky - slider na homepage, pri nahravani stranky to stahuje vsechny obrazky ktere mate nastavene. pokud jich mate nastavenych 10, tak se jich stahne deset. Idealni je upravit nacitani na lazy load. - zbytecne moduly: odstrante vse co jde, kazdy modul navic zpomaluje nacitani
  10. Nezkusil, ani jsem netusim ze je neco takoveho k dispozici. Ja to prozatim udelal tak, ze jsem si na barvy udelal vlastni modul, vyuzivajici klasicky search controller. Jake to ma mit vylepseni? A je to skutecne uz funkcni oprava, nebo je to jen o trochu rychlejsi?
  11. Schvalne se zkuste na ten filtr podivat i na jinych vlaknech fora, co jsem nasel tak si vsichni stezovali ze je spatne udelany. Nepouziva totiz cache a data taha primo z databaze komplikovanym dotazem, a prave to zpusobuje to zpomaleni (na nasem serveru tento jeden dotaz trval 10 sekund, jine jsou v radu milisekund takze db je v poradku). Vetsinou vsichni udajne skoncili u Advanced Filter Pro 4, ale ten stoji tusim nejakych 250$ coz neni zrovna levna zalezitost. S tim APC to ale skutecne funguje, jediny problem je, ze presta se snazi cachovat prakticky vsechno, a pri vetsim mnozstvi produktu a pri vetsi navstevnosti se zacne strasne rychle cache fragmentovat. Pro kazdou navstivenou stranku s produktem to vytvorilo priblizne 100-200 promennych, u velkych kombinaci i vic. Vynasobte poctem produktu a zjistite ze to je uz mnohem vic, nez dokaze pamet udrzet.
  12. Jestli vam to situace dovoli, zkuste nechat na serveru APC zapnute, v BO APC vypnout a projdete si ruzne stranky, treba testem jako webpagetest nebo gtmetrix. Podle mych testu je homepage a product page nactena hluboko pod dve sekundy, jen ty kategorie kde je blocklayered zapnuty nacitaji 10-15 vterin. Kdyz zapnu APC i v BO, tak je to za 2 sekundy. Timhle testem jsem zjistil ze prave ten filter je pricinou a podle ostatnich adminu jim to dela taky ve chvili kdy maji hlavne ty kombinace. My mame neco malo pres 2000 produktu, kombinace jen barvu a u prstenu velikosti (ty prave delaji poradne mnozstvi kombinaci, protoze damska/panska velikost vytvari velke mnozstvi moznosti). Kdyz sem APC vypnul i na serveru, tak ta rychlost klesla vsude na osklive cisla. Takze souhlasim s vami, bez APC to moc nejde. Pokud se vam ale zacne obchod zpomalovat, zamerte se na filtr
  13. Ja to prave taky zkousel hnat do extremu az jeden giga, ale po tech tydnech googlovani, konfigurovani a zkouseni mi postupne vsechno "docvaklo". Kdykoliv nekde doporucovali nejakou konkretni konfiguraci APC, tak meli fragmentaci i nulovou. Toho jsem docilil jen ve chvili, kdy jsem v backofficu APC vypnul. Vsechny stranky fungovalyu mozna jeste o zdibec rychleji, krome kategorii, kde je blocklayered. Tady bych se zeptal: pouzivate tento modul? Kolik mate produktu a kombinaci? Podle ostatnich to zacne drasticky snizovat vykon s rostoucim poctem produktu a hlavne atributu. Ja se ted chystam tohodle modulu zbavit, cimz vyresim i problemy s APC, ale nejdriv musim zrejme modul sam udelat, protoze free alternativu jsem nikde nenasel. A rotoze potrebujem stejne jen filtry podle barev, tak by to nemelo byt tak tezke. Kazdopadne to cachovani v preste je fakt nejake divne, lepsi je to bez neho.
  14. Hello, I have a tricky question: Is it possible to disable cache (APC in my case) in prestashop BO to stop floofing APC by useless user cache entries, AND force some modules/files to still use the cache? My problem is that enabling APC in BO is useless and in fact slower the performance of site. Except of blocklayered module, this one is much faster with cache enabled. So I was curious if there is in php source code something like if (cache.isEnabled) -> set/get variable from cache else -> set/get variable where removing the condition will force to use the cache which is set correctly on server of course. Till I found some alternative for blocklayered module, this is the only solution I have on my mind at this moment... Thanks
  15. Hello, because blocklayered module is not working properly and is really slow, I am looking for free alternative. My expectations are not high, we want just simple block in left column with checkbox list of available color attributes for current category so visitor can filter 0-n colors in product list. Is there something similar? Or some workaround/blocklayered module modification? We don't need any other feature, just color filtering. I would appreciate any hints or suggestions, thanks.
×
×
  • Create New...