XF 1.3 uploading an add-on take ages when (run-deferred)

TBDragon

Active member
hi every one

i have strange issue with run-deferred while uploading new/upgrading an add-ons
and even while upgrading XF

this issue in both my live & local forum

its take around 20 to 45min ! to just upgrade an addon

and for upgrading for XF its take around 1h =(

is this normal ?!

i just have 3 style ( default - UI.X - Child of UI.X )

does it depend on the number of styles ?!or number of addons on my forum !!
 
hi every one

i have strange issue with run-deferred while uploading new/upgrading an add-ons
and even while upgrading XF

this issue in both my live & local forum

its take around 20 to 45min ! to just upgrade an addon

and for upgrading for XF its take around 1h =(

is this normal ?!

i just have 3 style ( default - UI.X - Child of UI.X )

does it depend on the number of styles ?!or number of addons on my forum !!

I can't imagine it taking 20 minutes to update an add on, let alone 45 minutes. It should only take a minute to two minutes at the latest.

Maybe you should open up a ticket in the customer area and provide log in details so that a staff member can look into it. - http://xenforo.com/customers/
 
If it's taking that long then it's going to be server related.
It could be a combination of the database engine, server configuration, settings, etc.
 
If it's happening in localhost then your machine spec's or WAMP config are to blame.

My localhost rebuild with 3 styles and 22 add-ons takes about 30 seconds.
 
If it's happening in localhost then your machine spec's or WAMP config are to blame.

My localhost rebuild with 3 styles and 22 add-ons takes about 30 seconds.


will my laptop is 6gb ram and i7

any way

for my vps
its 1 gb ram
I have around 35 addons

how I can know that the issue from the server and how to solve it
I follow the openlitespeed instructions in the RM :(

thanks for reply if its not related to addons or style or XF then I cant open ticket , I will try to see how to solve the server issue :'(
 
Or just set a custom HOSTS entry pointing at the localhost. I do basically the same thing for my local servers (twd.alpha and twd.beta or nsl.alpha and nsl.beta) for my test sites that I sometimes utilize. That way I can also use hostnames in my test site and test any rewrites that I'm working on (domain A to domain B, etc).
 
Top Bottom