Jump to content

500hz vs.1000hz polling rate

Ruben360

Hey,

I have a logitech g403 wireless and there is an option to choose between diffrent polling rates.

Is 1000hz worth the 1h reduced battery life? 

Thanks

Link to comment
Share on other sites

Link to post
Share on other sites

4 minutes ago, TheGlenlivet said:

Do you need the dank 360 no scope 300 fps craziness :ph34r:?  If no then leave it at 500.

I mean I do my dank 360 no scopes from time to time, but I think ill stick to 500hz.

Link to comment
Share on other sites

Link to post
Share on other sites

18 minutes ago, TheGlenlivet said:

Do you need the dank 360 no scope 300 fps craziness :ph34r:?  If no then leave it at 500.

what has the maus polling rate to do with your dpi?

i have tried booth and use my mouse with 400 dpi and i experience no difrence it is a bit krisp but not realy noticable

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, ianspy1 said:

what has the maus polling rate to do with your dpi?

i have tried booth and use my mouse with 400 dpi and i experience no difrence it is a bit krisp but not realy noticable

DPI is like distance scaling. Basically the sensitivity of the mouse, high DPI means more sensitive (smaller mouse movement = larger pointer movement). Polling rate is how often the mouse reads it's location.

 

It's not exactly the same but DPI is kinda like monitor resolution, while polling rate is like monitor refresh rate.

Primary PC-

CPU: Intel i7-6800k @ 4.2-4.4Ghz   CPU COOLER: Bequiet Dark Rock Pro 4   MOBO: MSI X99A SLI Plus   RAM: 32GB Corsair Vengeance LPX quad-channel DDR4-2800  GPU: EVGA GTX 1080 SC2 iCX   PSU: Corsair RM1000i   CASE: Corsair 750D Obsidian   SSDs: 500GB Samsung 960 Evo + 256GB Samsung 850 Pro   HDDs: Toshiba 3TB + Seagate 1TB   Monitors: Acer Predator XB271HUC 27" 2560x1440 (165Hz G-Sync)  +  LG 29UM57 29" 2560x1080   OS: Windows 10 Pro

Album

Other Systems:

Spoiler

Home HTPC/NAS-

CPU: AMD FX-8320 @ 4.4Ghz  MOBO: Gigabyte 990FXA-UD3   RAM: 16GB dual-channel DDR3-1600  GPU: Gigabyte GTX 760 OC   PSU: Rosewill 750W   CASE: Antec Gaming One   SSD: 120GB PNY CS1311   HDDs: WD Red 3TB + WD 320GB   Monitor: Samsung SyncMaster 2693HM 26" 1920x1200 -or- Steam Link to Vizio M43C1 43" 4K TV  OS: Windows 10 Pro

 

Offsite NAS/VM Server-

CPU: 2x Xeon E5645 (12-core)  Model: Dell PowerEdge T610  RAM: 16GB DDR3-1333  PSUs: 2x 570W  SSDs: 8GB Kingston Boot FD + 32GB Sandisk Cache SSD   HDDs: WD Red 4TB + Seagate 2TB + Seagate 320GB   OS: FreeNAS 11+

 

Laptop-

CPU: Intel i7-3520M   Model: Dell Latitude E6530   RAM: 8GB dual-channel DDR3-1600  GPU: Nvidia NVS 5200M   SSD: 240GB TeamGroup L5   HDD: WD Black 320GB   Monitor: Samsung SyncMaster 2693HM 26" 1920x1200   OS: Windows 10 Pro

Having issues with a Corsair AIO? Possible fix here:

Spoiler

Are you getting weird fan behavior, speed fluctuations, and/or other issues with Link?

Are you running AIDA64, HWinfo, CAM, or HWmonitor? (ASUS suite & other monitoring software often have the same issue.)

Corsair Link has problems with some monitoring software so you may have to change some settings to get them to work smoothly.

-For AIDA64: First make sure you have the newest update installed, then, go to Preferences>Stability and make sure the "Corsair Link sensor support" box is checked and make sure the "Asetek LC sensor support" box is UNchecked.

-For HWinfo: manually disable all monitoring of the AIO sensors/components.

-For others: Disable any monitoring of Corsair AIO sensors.

That should fix the fan issue for some Corsair AIOs (H80i GT/v2, H110i GTX/H115i, H100i GTX and others made by Asetek). The problem is bad coding in Link that fights for AIO control with other programs. You can test if this worked by setting the fan speed in Link to 100%, if it doesn't fluctuate you are set and can change the curve to whatever. If that doesn't work or you're still having other issues then you probably still have a monitoring software interfering with the AIO/Link communications, find what it is and disable it.

Link to comment
Share on other sites

Link to post
Share on other sites

dpi is short for dots per inch ... in very simple terms is how precise the mouse can detect motion ... think of the mouse taking an inch wide picture of the mouse pad under it and that picture will have that many dots horizontally ... so when you move the mouse slightly and the mouse takes another picture, the mouse knows it moved that many pixels in some direction

 

the polling rate is how often the mouse reports to the computer that it moved or that a button was pressed, scroll wheel rotated etc.. basically any state change.

 

USB works in a funny way ... the computer (the usb controller actually) has to ask each device plugged in an usb port "Do you have some data to give me?" and only then the device is allowed to reply with "Yes, here's the data" or "No, nothing new"

By design, USB will ask any device up to 125 times a second (125 Hz polling rate) but this number can be increased up to 1000, that's what 1000 Hz polling rate means.

The extra polling rate makes the usb controller chip work harder and the usb driver on the computer will also use a bit more CPU processing power but with modern processors it's fairly insignifiant.

 

So 500 hz vs 100 hz ... let's say you move your mouse 1 inch in 10 ms and you move it very smoothly and constant speed.

With 500 hz polling rate, that means the computer will receive one update every 2 ms, so the computer will receive 5 updates, and each update will say "mouse moved one fifth of an inch this way".

With 1000 hz polling rate, that means one update every ms, so  in those 10ms, the computer will receive 10 updates, each saying "the mouse moved one tenth of an inch this way"

 

it's up to the game or software if it's actually capable to do something with that information, if the game actually cares that you tell it 500 times a second, or 1000 times a second how much the mouse moved.

 

With wireless mice, most likely the dongle actually sets the polling rate at 1000hz but the mouse itself will only send through the air updates to the dongle only 500 times a second. Wireless transmission consumes power, so naturally 500 bursts of energy will waste less battery compared to 1000 bursts of energy each second.

The dongle doesn't care about power consumption , since it's powered from the usb port... 

 

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

19 hours ago, pyrojoe34 said:

DPI is like distance scaling. Basically the sensitivity of the mouse, high DPI means more sensitive (smaller mouse movement = larger pointer movement). Polling rate is how often the mouse reads it's location.

 

It's not exactly the same but DPI is kinda like monitor resolution, while polling rate is like monitor refresh rate.

i know that but he said he needs more polling for fliks what makes no sense

Link to comment
Share on other sites

Link to post
Share on other sites

2 hours ago, ianspy1 said:

i know that but he said he needs more polling for fliks what makes no sense

Sure it does. If a flick takes 1/100th of a second and your polling rate is too low you might get a slight lag or inaccuracy if you don't read the position enough times. It's the exact reason you want high refresh rate in fast paced games, so you don't miss important information that happens in a fraction of a second. Polling rate of 500hz means an inherent 2ms delay while 1000hz means 1ms delay from the sensor. Let's say you draw a circle with 500 connected dots vs a circle with 1000 connected dots, the one with 1000 will look smoother and look more like a smooth circle than the one with 500 dots.

Primary PC-

CPU: Intel i7-6800k @ 4.2-4.4Ghz   CPU COOLER: Bequiet Dark Rock Pro 4   MOBO: MSI X99A SLI Plus   RAM: 32GB Corsair Vengeance LPX quad-channel DDR4-2800  GPU: EVGA GTX 1080 SC2 iCX   PSU: Corsair RM1000i   CASE: Corsair 750D Obsidian   SSDs: 500GB Samsung 960 Evo + 256GB Samsung 850 Pro   HDDs: Toshiba 3TB + Seagate 1TB   Monitors: Acer Predator XB271HUC 27" 2560x1440 (165Hz G-Sync)  +  LG 29UM57 29" 2560x1080   OS: Windows 10 Pro

Album

Other Systems:

Spoiler

Home HTPC/NAS-

CPU: AMD FX-8320 @ 4.4Ghz  MOBO: Gigabyte 990FXA-UD3   RAM: 16GB dual-channel DDR3-1600  GPU: Gigabyte GTX 760 OC   PSU: Rosewill 750W   CASE: Antec Gaming One   SSD: 120GB PNY CS1311   HDDs: WD Red 3TB + WD 320GB   Monitor: Samsung SyncMaster 2693HM 26" 1920x1200 -or- Steam Link to Vizio M43C1 43" 4K TV  OS: Windows 10 Pro

 

Offsite NAS/VM Server-

CPU: 2x Xeon E5645 (12-core)  Model: Dell PowerEdge T610  RAM: 16GB DDR3-1333  PSUs: 2x 570W  SSDs: 8GB Kingston Boot FD + 32GB Sandisk Cache SSD   HDDs: WD Red 4TB + Seagate 2TB + Seagate 320GB   OS: FreeNAS 11+

 

Laptop-

CPU: Intel i7-3520M   Model: Dell Latitude E6530   RAM: 8GB dual-channel DDR3-1600  GPU: Nvidia NVS 5200M   SSD: 240GB TeamGroup L5   HDD: WD Black 320GB   Monitor: Samsung SyncMaster 2693HM 26" 1920x1200   OS: Windows 10 Pro

Having issues with a Corsair AIO? Possible fix here:

Spoiler

Are you getting weird fan behavior, speed fluctuations, and/or other issues with Link?

Are you running AIDA64, HWinfo, CAM, or HWmonitor? (ASUS suite & other monitoring software often have the same issue.)

Corsair Link has problems with some monitoring software so you may have to change some settings to get them to work smoothly.

-For AIDA64: First make sure you have the newest update installed, then, go to Preferences>Stability and make sure the "Corsair Link sensor support" box is checked and make sure the "Asetek LC sensor support" box is UNchecked.

-For HWinfo: manually disable all monitoring of the AIO sensors/components.

-For others: Disable any monitoring of Corsair AIO sensors.

That should fix the fan issue for some Corsair AIOs (H80i GT/v2, H110i GTX/H115i, H100i GTX and others made by Asetek). The problem is bad coding in Link that fights for AIO control with other programs. You can test if this worked by setting the fan speed in Link to 100%, if it doesn't fluctuate you are set and can change the curve to whatever. If that doesn't work or you're still having other issues then you probably still have a monitoring software interfering with the AIO/Link communications, find what it is and disable it.

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, pyrojoe34 said:

Sure it does. If a flick takes 1/100th of a second and your polling rate is too low you might get a slight lag or inaccuracy if you don't read the position enough times. It's the exact reason you want high refresh rate in fast paced games, so you don't miss important information that happens in a fraction of a second. Polling rate of 500hz means an inherent 2ms delay while 1000hz means 1ms delay from the sensor. Let's say you draw a circle with 500 connected dots vs a circle with 1000 connected dots, the one with 1000 will look smoother and look more like a smooth circle than the one with 500 dots.

i still dont get it xD

 

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×