Octave runs more slowly after force quit - performance

I am running Octave 6.2.0. I have had to force quit the software after it became unresponsive while I moved its window across monitors, and since then any code I run takes much longer than it used to.
I run the same script with profile on on the "newly" slow computer and another laptop. Dlmread and fprintf make up for over 99% of execution time for the script, so I just compared times for those two functions.
Test 1: Octave 6.2.0 (after crash) on Dell Precision 3640 (Core i7-10700 # 2.9 GHz, 64 GB RAM) with Windows 10 Pro, from SSD.
Test 2: Octave 6.2.0 (after crash) on Dell Precision 3640 (Core i7-10700 # 2.9 GHz, 64 GB RAM) with Windows 10 Pro, from HDD.
Test 3: Octave 5.2.0 (for comparison) on Dell Inspiron 5570 (Core i7-8550U # 1.8 GHz, 32 GB RAM) with Windows 10 Pro, from HDD.
+--------+------------------+------------------+-----------------------+
| | dlmread time (s) | fprintf time (s) | Total script time (s) |
+--------+------------------+------------------+-----------------------+
| Test 1 | 138 | 249 | 388 |
+--------+------------------+------------------+-----------------------+
| Test 2 | 138 | 278 | 417 |
+--------+------------------+------------------+-----------------------+
| Test 3 | 48 | 45 | 93 |
+--------+------------------+------------------+-----------------------+
I tried uninstalling and reinstalling, clearing cache and preferences, installing an older version of Octave, but nothing seems to solve the problem.
Any idea of what may have gone wrong and anything else I could do to troubleshoot?
A similar issue is described in this post, but no solution was posted in that case: Octave suddenly running scripts slowly after crash.

Related

Error: The test runner exited with code -1 before checking in

After build finishes without issue, running Xcode 12.4 project's tests fail with message:
MyProject.app (10164) encountered an error (
Early unexpected exit,
operation never finished bootstrapping - no restart will be attempted. (
Underlying Error: The test runner exited with code -1 before checking in.
If you believe this error represents a bug,
please attach the result bundle at /Users/admin/Library/Developer/Xcode/DerivedData/MyApp-gczfeuobxydqjrfbdhwzpqjsseyr/Logs/Test/Test-MyApp-2021.09.29_23-12-38-+0430.xcresult
)
)
What is above message trying to mean?!
(parenthesis spacing is by me, to make human-readable)
About My System: macOS Catalina version 10.15.7 (19H2)
MacBook Pro (13-inch, Mid 2010)
Processor 2.4 GHz Intel Core 2 Duo
Memory 4 GB 1067 MHz DDR3
Graphics NVIDIA GeForce 320M 256 MB
TK;DR; Either update MacOS to latest, or downgrade Xcode to 11.7 version.
At last I found reason, seems Xcode 11.7 (or rather it's SDK), is the last version which supports running on Catalina version of MacOS
(without any manual extra effort).
But running tests for iOS device works (without macOS update).
Someone please tell Apple to improve their error messages :-(

How to fix "Prefix creation exited with error" in Wine at mac?

When I install a .exe application in WineBottler,it shows an error "Prefix creation exited with error"
There is the error log:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro15,2
Processor Name: Intel Core i5
Processor Speed: 2.3 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Hyper-Threading Technology: Enabled
Memory: 8 GB
Boot ROM Version: 1037.0.52.0.0 (iBridge: 17.16.10531.5.4,0)
Activation Lock Status: Enabled
###BOTTLING### Create .app...
###BOTTLING### Enabling CoreAudio, Colors, Antialiasing and flat
menus...
/Applications/WineBottler.app/Contents/Frameworks/WBottler.framework/Resources/bottler.sh: line 143:
/Applications/Wine.app/Contents/Resources/bin/wine: Bad CPU type in executable
### LOG ### Command '/Applications/Wine.app/Contents/Resources/bin/wine regedit /tmp/reg.reg' returned status 126.
###ERROR### Command '/Applications/Wine.app/Contents/Resources/bin/wine regedit /tmp/reg.reg' returned status 126.
Task returned with status 1.
EDIT (27.10.19) : It works also with Mojave but you still get a few errors. If you downgrade to High Sierra, it will work perfectly. Just be sure that you download the last STABLE Version of Wine (4.0.2) and also install winetricks.
I'm guessing you're using the last OS version (Catalina).
From what I've found so far, 32-bit program support is going away on the Mac with Catalina, and atm there is no viable solution for this issue.
RN, I'm facing the same issue.
Still, I've found some kind of a workaround. Install wine via brew, use a 64bit version of the .exe that you're trying to install, and run the following command:
wine64 <your_program.exe>
If that still doesn't work, try downgraiding to Mojave, since it's the last OS version that supports 32bit apps. (That's what I'm going to do in the next few days, and I'll come back with an update)
Hope it helps !

GPU compute cluster faster on Windows 10 than Ubuntu 18.04

Info: My windows and Ubuntu system is the same. I just swap out my boot drive using a removable drive bay.
*Not using Docker
CPU: i9-7920X (128 GB DDR4)
GPUs:
2 Titan Vs and
RTX 2070 (Display)
Windows 10:
Nvidia Driver 416.81 in TCC cluster and
Cuda 10
Ubuntu Desktop 18.04:
Nvidia Driver 410.72 (not sure if need to cluster on Linux) and
Cuda 10
Test Software:
Running TensorFlow cifar10 esitimator - same training data - (link at bottom)
python cifar10_main.py --data-dir=/tmp --job-dir=/tmp/cifar10 --num-gpus=2 --train-steps=10000
Windows completes in 420 seconds (7.0 minutes)
Ubuntu completes in 614 seconds (10.2 minutes)
https://github.com/tensorflow/models/tree/master/tutorials/image/cifar10_estimator
Why is Ubuntu so much slower? Do the GPUs need to be clustered on Linux or are the different drivers (Ubuntu vs. Windows) the issue?
Thanks.

Homebrew install node - make taking too long

Should it take forever to install node.js using Homebrew? I've attempted several times, even leaving it running overnight, and it has never completed. I'm doing it again now in verbose mode, and it's printing endless 'clang' lines. It's not erroring out, but am I doing something wrong, or should I just use the package installer?
Running OS X 10.8 on a Retina MacBook Pro (2.4 GHz, 16 GB RAM)

Installing qt5 Taking a long time with Brew [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
Has anyone had the problem of installing qt5 taking longer than expected?
gerudian:vra-rails alvincrespo$ brew doctor
Your system is ready to brew.
gerudian:vra-rails alvincrespo$ brew install qt5
==> Downloading http://releases.qt-project.org/qt5/5.0.2/single/qt-everywhere-opensource-src-5.0.2.tar.gz
Already downloaded: /Library/Caches/Homebrew/qt5-5.0.2.tar.gz
==> ./configure -prefix /usr/local/Cellar/qt5/5.0.2 -system-libpng -system-zlib -confirm-license -opensource -nomake demos -nomake examples -arch x86_64 -release
==> make
it took 29 minutes for me, on a MacBook Pro i7 16G RAM with SSD.
Mine took over six hours... mid-2011 Mac mini i5 (dual core) 8GB RAM
brew reinstall qt5 --with-docs --with-examples
/usr/local/Cellar/qt5/5.5.1_2: 26,937 files, 876M, built in 385 minutes 26 seconds
1.5 hrs for me on my Mid-2010 MacBook Pro 2.66GHz i7 4GB memory:
/usr/local/Cellar/qt/4.8.6: 2793 files, 121M, built in 87.4 minutes
The result on my MacBook Pro Core i5 at 2.3GHz with 4GB RAM was:
/usr/local/Cellar/qt/4.8.6: 2791 files, 121M, built in 76.6 minutes
Results from a Late 2013 Mac Pro, 12 2.7 Ghz cores and 64 GB of ECC RAM:
🍺 /usr/local/Cellar/qt5/5.4.0: 6310 files, 287M, built in 27.2
minutes
Results from a Mid 2013 Macbook Air w/ 1.3 GHz dual-core i5 (4250U) with 4 GB of RAM.
/usr/local/Cellar/qt5/5.4.0: 6310 files, 285M, built in 187.7 minutes
I gotta say, I almost gave up around the 2 hour mark.
My results on Mid-2009 MacBook Pro with 2,53 GHz Intel Core 2 Duo und 8 GB ram.
🍺 /usr/local/Cellar/qt5/5.4.0: 24683 files, 756M, built in 427.5 minutes
That's more than 7 hours! Why did it take that long?
Probably because I compiled with these options:
brew install qt5 --with-docs --with-examples --with-developer --with-d-bus
It took nearly 1.5 hours on a Late-2008 MacBook Pro Core 2 Duo at 2.8GHz with 8GB of memory!
🍺 /usr/local/Cellar/qt/4.8.6: 2793 files, 119M, built in 82.7 minutes
White 2008 penryn macbook 2.4GHz Core 2 Due with 2GB RAM:
/usr/local/Cellar/qt/4.8.7_1: 2795 files, 121M, built in 147.0 minutes
pyqt was another ~20 min on top.

Resources