Development discussion of WireGuard
 help / color / mirror / Atom feed
From: kolargol <kolargol@protonmail.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: iOS WG Battery Life
Date: Thu, 28 Feb 2019 12:07:07 +0000	[thread overview]
Message-ID: <zk1gAdr9rlJCh4vzh4DYSc11v_Ja4r_9xYurdAcwFsa50g2zMxHskd5Nb0leXZKUZrCqV3YIZFI5pNYptUGXTyQBIl5zWoF_N306lQKO_tg=@protonmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 555 bytes --]

Hi

Thanks for great work with Wireguard, it's fresh breeze of air compared on years spend on OpenVPN...

I am testing WG on varius OSes and devices and I have noted severe battery drain on iOS (12.2, iPhone 8). Typically battery drops 40% during night-time (that is 7 hours of inactivity on the phone) when WireGuard is engaged.
Is this some kind of known issue? I did not had chance to test previous iOS version without SIMD ChaCha20 support so i cannot tell if it is becouse of the last update.

Anything i can do to track issue here?

thanks,
kolargol

[-- Attachment #1.2: Type: text/html, Size: 711 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

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

             reply	other threads:[~2019-03-01 10:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 12:07 kolargol [this message]
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
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='zk1gAdr9rlJCh4vzh4DYSc11v_Ja4r_9xYurdAcwFsa50g2zMxHskd5Nb0leXZKUZrCqV3YIZFI5pNYptUGXTyQBIl5zWoF_N306lQKO_tg=@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).