Development discussion of WireGuard
 help / color / mirror / Atom feed
From: kolargol <kolargol@protonmail.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: iOS WG Battery Life
Date: Sun, 03 Mar 2019 15:30:09 +0000	[thread overview]
Message-ID: <4XNSL3x5-sa87nwSeyuursmJhUSP47KlBZtZMKKZ2xeCLmWAAG1o-sP_6J7TUcfustGCSPack_u_6C1ase8n_ZuUqPA-FhqbfnBoEjMGEqg=@protonmail.com> (raw)
In-Reply-To: <58158D37-9937-4BA2-B89B-A63DF8BA03A1@pcfreak.de>

> what about uninstalling all vpns and try over night?

i will test that as well.

Meanwhile wile plumbing over iOS I have found possible reason of thos. Seems like Wireguard suffers from thread management problems:

Event:           wakeups
Action taken:    none
Wakeups:         45001 wakeups over the last 61 seconds (743 wakeups per second average), exceeding limit of 150 wakeups per second over 300 seconds
Wakeups limit:   45000
Limit duration:  300s
Wakeups caused:  45001
Duration:        30.33s
Steps:           2

quite a lot? bad for battery - there are multiple crashes due to this limit on my iOS. I can send full crash log to developers (just ping me).

Other then that i installde debug profiles for VPN and Networking on iOS, will try to dig tomorrow after another night test.

thanks,
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-03-03 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 12:07 kolargol
2019-03-01 10:08 ` Kalin KOZHUHAROV
2019-03-02  0:30   ` Mark Finzel
2019-03-02  7:29   ` kolargol
     [not found]     ` <EA2CDA40-8988-4C4F-B848-B2F7C6D8716C@lonnie.abelbeck.com>
2019-03-02 19:54       ` kolargol
2019-03-02 20:09         ` John
2019-03-02 20:50         ` Mailing Lists
2019-03-03 15:30           ` kolargol [this message]
2019-03-02 21:22         ` Lonnie Abelbeck
2019-03-06 10:32 ` kolargol

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='4XNSL3x5-sa87nwSeyuursmJhUSP47KlBZtZMKKZ2xeCLmWAAG1o-sP_6J7TUcfustGCSPack_u_6C1ase8n_ZuUqPA-FhqbfnBoEjMGEqg=@protonmail.com' \
    --to=kolargol@protonmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).