Saturday, March 5, 2016
Thursday, December 31, 2015
Monday, November 2, 2015
Thursday, October 1, 2015
Tuesday, July 14, 2015
When you have a machine like I do that has a CPU capable of
Turbo or other overclocking, then one may want to only “activate it” when really needed. This way one can avoid unnecessary fan spinups and heat.
My default CPU clock is at 2.8Ghz and capable to boost up to 3.6Ghz. To avoid always going back to the
BIOS and turn the
Turbo feature on and off, I have found an easier way to throttle down frequency within the
Power options menu.
On this video I show you an easy way to create a custom power scheme and set the CPU throttle values:
As shown on the video you can realise it’s only to change the CPU speed from 100% (with Turbo) to 99% to throttle it to the default frequency. It’s just that 1%, really! :)
To further modify/delete power schemes you really have to go to the command line.
To delete a scheme:
First let’s list all of the schemes to get their UUID:
results in the list:
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced) Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High performance) Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a (Power saver) Power Scheme GUID: dc512798-8638-4c98-9432-5e0e744ab01b (Game) *
Let’s delete Power Saver (you can’t delete the current one, marked with *):
powercfg /d a1841308-3541-4fab-bc81-f71556f20b4a
Changing power schemes with a click of the mouse
You can also create a few shortcuts to change between power schemes with just a line like this as the command:
cmd /c "powercfg /s dc512798-8638-4c98-9432-5e0e744ab01b"
This is useful when you use more than 2 schemes, because the taskbar icon only let’s you change between the most recent 2 of them.
Written with StackEdit.
Monday, March 16, 2015
This tutorial is based on using Vmware Workstation 11 on Windows 8.1 host using an Ubuntu 14.04 guest. Note: you have to have the vmware tools, client additions installed on the quest machine!
First go to the Vmware client's terminal when you are ready to shrink it down and type:
sudo vmware-toolbox-cmd disk list
This will give you the mount points that can be shrinked individually.
For me I will only go with shrinking the main disk with "/" (root).
First lets wipe the free space clean so the shrinker will know what is free to get rid of:
sudo vmware-toolbox-cmd disk wipe /
sudo vmware-toolbox-cmd disk shrink /
That's it, after the process in my case I've had a 4.4G file shrinked down to 1.7G, which is much closer to what the client OS saw (1.5G).
Friday, March 6, 2015
Ok now, let's see how these tags translate on the report UI.
First we are seeing failed results.
ConclusionThe source XSD file I used to figure out how the JUnit XML should look like can be found here. Although the XSD suggests a far more feature rich XML structure, only a minor portion of that information is used by Jenkins. :(
Monday, November 17, 2014
The trick here is to use the correct heredoc format with defining the language inside the string.
Monday, October 20, 2014
Here is a small GIST example for a simple, non-splitting window setup:
Friday, August 15, 2014
Monday, September 9, 2013
- when the app is constantly saving what the user inputs
- when it is just done saving every piece of data
- when some time passed and it wants to inform the user about real time status information
I hope this little code gives some of you more ideas. Please bare with this code as it is premature and not yet ready for production (I believe).
Thursday, March 28, 2013
export PATH=$PATH:/home/ikon/binThis way my ~/bin directory is added to the system path. Check it with
$ echo $PATH
Saturday, February 9, 2013
Version ruby 1.9.3-p327 using RVM, debugger and debugger-linecache restisted the bundle install command.
gem install debugger-linecache -v '1.1.2' -- --with-ruby-include=\$rvm_path/src/ruby-1.9.3-p374
gem install debugger -v '1.2.3' -- --with-ruby-include=\$rvm_path/src/ruby-1.9.3-p374