Modify

Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#11755 closed defect (worksforme)

High CPU load uhttpd

Reported by: anonymous Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: uhttpd cpu load Cc:

Description

Hi, i flashed on wr1043nd with OpenWrt Attitude Adjustment r32130, i use uhttpd with https support. I noticed in the processes status from Luci, that uhttpd has high cpu load, about 85-97 %, either in http than https use. How can i fix it? Thanks

Attachments (0)

Change History (14)

comment:1 Changed 6 years ago by jow

  • Resolution set to wontfix
  • Status changed from new to closed

Yes, uhttpd will cause cpu load while it runs to show the cpu load, you cannot fix that.

comment:2 Changed 6 years ago by rechapita@…

  • Resolution wontfix deleted
  • Status changed from closed to reopened

I think there is an actual bug here.
I checked via ssh+top: when idle (no one connected to the webif) uhttpd is taking at least 15% cpu load on my setup.

comment:3 Changed 6 years ago by jow

  • Resolution set to worksforme
  • Status changed from reopened to closed

Works here, 0% when idle.

comment:4 Changed 6 years ago by anonymous

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Happening here too, but only when displaying Status/Overview page. Usually the uhttpd process caps out at 12-15% cpu, load averages climb to crazy levels.

Just reflashed r32603, installed packages: luci nano luci-app-radvd luci-app-ddns luci-app-upnp

Screenshot: http://img807.imageshack.us/img807/3913/uhttpd.jpg

This didn't happen until recently (1-2 months ago?).

comment:5 Changed 6 years ago by jow

  • Resolution set to worksforme
  • Status changed from reopened to closed

Yes, it will use CPU while it serves requests - if its idle the load falls to 0%.

comment:6 Changed 6 years ago by anonymous

So it's considered normal that load average goes above 3.00 when checking the status page?

I was under the impression that checking the status page was something I could use to check the status of the device. If the process of displaying that data causes so much load that the box becomes a snail, what's the point of the status page?

comment:7 Changed 6 years ago by anonymous

Additionally, uhttpd cpu usage is around 10% while displaying most other pages, but load average will remain at close to 0.00 and the router will not become sluggish. It only happens on Status/Overview page...

comment:8 Changed 6 years ago by jow

Load average is 0.02 here while serving the status page, tested with a debug build of uhttpd on a wzr-hp-g300nh, wndr3700, wndr3700v2.

comment:9 Changed 6 years ago by anonymous

Tested without any extra packages installed apart from LuCI, same thing occurs using both Internet Explorer, Firefox and Chrome.

There is for sure something strange going on, be it a bug or not.

I just can't find a way to replicate it.. It doesn't happen every time I open the status page, and I'm not doing anything different when it does happen..

It seems to happen more often when I return from another page TO the status page, but that's as far as I've got.

comment:10 Changed 6 years ago by anonymous

I also run a TL-1043ND. In case that's relevant somehow..

comment:11 Changed 6 years ago by jow

r32640 should lower the observed load figures

comment:12 follow-up: Changed 4 years ago by anonymous

I am seeing 100% cpu load while the router should be idle. Doing an strace -p <pid> on uhttpd shows this:

epoll_wait(3, {{EPOLLIN, {u32=9613384, u64=41289169883889664}}}, 10, 0) = 1
clock_gettime(CLOCK_MONOTONIC, {1739521, 859483517}) = 0
epoll_wait(3, {{EPOLLIN, {u32=9613384, u64=41289169883889664}}}, 10, 0) = 1
clock_gettime(CLOCK_MONOTONIC, {1739521, 859841320}) = 0
epoll_wait(3, {{EPOLLIN, {u32=9613384, u64=41289169883889664}}}, 10, 0) = 1

(in an endless loop)

Using attitude-adjustment on a wdr-3600.

comment:13 in reply to: ↑ 12 Changed 4 years ago by bittorf@…

(in an endless loop)

Using attitude-adjustment on a wdr-3600.

please give an exact revision-number.

comment:14 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.