Thread of PC Woes, Troubles, Problems, and Issues

There's nothing wrong with the formula, that's the thing.

A1=100,B1=100,C1=FALSE (formula=EXACT(A1,B1))

Despite the cells A1 & B1 being the same, the formula isn't updating to TRUE - only when I manually type the number in either cell does it update, or when I click top to edit the formula and press enter.


I have a suspicion this is because the data is being inserted (while file closed), and Excel isn't a change happening to the cells since last save.

Is the data type set to general, text or number?
 
[MENTION=6600]PsychoFish[/MENTION] - not to worry, one of the devs figured it out. Their code wasn't recalculating formulas upon insert.
 
So I reloaded my Windows 10 gaming machine at home the other night and spent some time getting it usable again. So I left it on overnight to do downloads, updates, etc. Woke up this morning to find that it had restarted.

Looking at the event logs this is what I found:
  1. The Sync Host_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
  2. The Contact Data_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
  3. The User Data Storage_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
  4. The User Data Access_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
  5. A timeout was reached (30000 milliseconds) while waiting for the User Data Storage_Session1 service to connect.
  6. A timeout was reached (30000 milliseconds) while waiting for the Sync Host_Session1 service to connect.

This was happening before the reload and I'm battling to pinpoint the problem.

Any ideas or suggestions? (can provide detailed stack if needed for each event).
 
So I reloaded my Windows 10 gaming machine at home the other night and spent some time getting it usable again. So I left it on overnight to do downloads, updates, etc. Woke up this morning to find that it had restarted.

Looking at the event logs this is what I found:
  1. The Sync Host_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
  2. The Contact Data_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
  3. The User Data Storage_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
  4. The User Data Access_Session1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
  5. A timeout was reached (30000 milliseconds) while waiting for the User Data Storage_Session1 service to connect.
  6. A timeout was reached (30000 milliseconds) while waiting for the Sync Host_Session1 service to connect.

This was happening before the reload and I'm battling to pinpoint the problem.

Any ideas or suggestions? (can provide detailed stack if needed for each event).

Disable OneSyncSvc service should fix that
 
I'm having an issue with Excel where it doesn't seem to be updating the formula. Upon normal use by manually entering codes (data) into cells the formula works 100%.

Here's the catch; because of the amount of codes we have to type in, we tried to simplify the process by creating a program to insert it into the cell (column). Obviously the file has to be closed while it writes to file. Now upon opening the file the formula doesn't apply/refresh.

It's just a simple formula of =EXACT(A1,B2) which outputs TRUE or FALSE.


Any ideas?
That part about writing to file sounds uber sketchy to me. Its unclear from you post exactly what you're doing but it sounds like a recipe for disaster to me. Are these .xls or xlsx?
 
Does anyone know of a way to speed up or increase performance, for a bunch of SQL scripts?


Our packages run thousands of insert scripts into database(s) and this process takes hours! Are there any tweaks I could make to try and decrease this time?
 
Does anyone know of a way to speed up or increase performance, for a bunch of SQL scripts?


Our packages run thousands of insert scripts into database(s) and this process takes hours! Are there any tweaks I could make to try and decrease this time?

It's going to depend on the script and the statements used. Some things just take forever.
 
Check for "SELECT *" type statements, hell, check for any statement that has a damn '*' in it, that's sure to slow things down.
 
Check for "SELECT *" type statements, hell, check for any statement that has a damn '*' in it, that's sure to slow things down.

Very little SELECT statements or '*'s in there, but a lot of INSERT, IF and WHERE.

Are there any tweaks I can make to CPU or RAM or something? like maybe set the affinity or something. Also worth mentioning we use PostgreSQL 8.x.

Now I have argued the point that inserting a SSD into the machine will decrease the wait period of said process by around 3x, would you agree or disagree here?
Personally I think the bottleneck are the drives, the read/write speeds are just not quick enough and therefor taking ~3 hours to run these queries.
 
Only one surefire way to prove it :-)

Essentially you want to do some monitoring/stats gathering on the device, specifically on the data drive, you want to look for a spike in Disk IO Wait times & Disk IO write latency

If you have significant spikes, then disk is the bottleneck. SSD will alleviate it, not always fix it.
 
Only one surefire way to prove it :-)

Essentially you want to do some monitoring/stats gathering on the device, specifically on the data drive, you want to look for a spike in Disk IO Wait times & Disk IO write latency

If you have significant spikes, then disk is the bottleneck. SSD will alleviate it, not always fix it.

qQiImFU.png
 
If the value of Avg. Disk Queue Length exceeds twice the number of spindles, then you are likely developing a bottleneck. With a volume set, a queue that is never shorter than the number of active physical disks indicates that you are developing a bottleneck.
 
[MENTION=6600]PsychoFish[/MENTION] - it should also be worth noting that this is not on an ESXi machine with VM's at all. This is on a single desktop PC dedicated for this purpose. Not a beast of a machine, just an okayish i7.

Also, CPU practically runs at 100% while this process is running.
 
[MENTION=6600]PsychoFish[/MENTION] - it should also be worth noting that this is not on an ESXi machine with VM's at all. This is on a single desktop PC dedicated for this purpose. Not a beast of a machine, just an okayish i7.

Also, CPU practically runs at 100% while this process is running.

Which is why I hate Doze, 100% CPU usage is a measure of what percentage your CPU's cycles are dedicated to running that one particular program. Which is why I prefer Linux load values like : load average: 0.09, 0.05, 0.01

Unix refers to this as the run-queue length: the sum of the number of processes that are currently running plus the number that are waiting (queued) to run. So on a Single core system with no HT 1.0 means I'm 100% utilized. 1.5 means I'm 100% utilized and 0.5 processes are queued to run still. MUCH more accurate than just looking at a %.a load of 1.00 is 100% CPU utilization on single-core box. On a dual-core box, a load of 2.00 is 100% CPU utilization. What is also nice is that it gives you a 1 minute, 5 minute and 15 minute value.

As an example, say an Intel Xeon E3-1285 which is Quad Core with HT. When I'm looking at the Linux load for a server with a single processor like that I'll worry about the CPU load if the 15 min average hits 8.0 and the 1 minute average if it goes over 16 I'm worried. For Windows though. Let me know if it hits 98% and chuck your toys at 100%, else I really don't care.
 
And in this morning meeting I was effectively told, "okay we won't bother with your SSD idea", cos they've found a way to make it a "bit quicker" by setting the application to use the processors cores.

Why do I even bother?!
 
Back
Top