While generating a large, long history, world my CPU held a 2.5GHz 'turboboost' and kept under 60C. Which made me wonder about if I could eek out more turning off Hyperthreading.
Lenovo Yoga 13 (original) with an Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz and 8GB (single channel) running 4.1.6-1-ARCH x86_64 with 'vanilla' DF 0.40.24 on a tmpfs 'RAM drive'
Before I wrote an .sh that would tie up my computer creating dozens of the same world I thought I should run a few tests. I heat soaked the computer by pregeneratnig a short (couple hundred years) world before each test.
Hyperthreading (on) it 'turboboosts' up to 2.5GHz stayed there and kept under 60C just like I saw before
Opens df, generates the world specified, saves it, closes df, reports the time it took;
$ time ./df -gen 100 9999 LONG
real 56m12.491s
user 56m37.826s
sys 0m19.073s
World gen profile (Large island 1050yr world);
[WORLD_GEN]
[TITLE:LONG]
[DIM:257:257]
[EMBARK_POINTS:1504]
[END_YEAR:1050]
[BEAST_END_YEAR:300:80]
[REVEAL_ALL_HISTORY:1]
[CULL_HISTORICAL_FIGURES:0]
[ELEVATION:1:400:1600:1600]
[RAINFALL:0:100:400:400]
[TEMPERATURE:25:75:400:400]
[DRAINAGE:0:100:400:400]
[VOLCANISM:0:100:400:400]
[SAVAGERY:0:100:400:400]
[ELEVATION_FREQUENCY:1:1:1:1:1:1]
[RAIN_FREQUENCY:1:1:1:1:1:1]
[DRAINAGE_FREQUENCY:1:1:1:1:1:1]
[TEMPERATURE_FREQUENCY:1:1:1:1:1:1]
[SAVAGERY_FREQUENCY:1:1:1:1:1:1]
[VOLCANISM_FREQUENCY:1:1:1:1:1:1]
[POLE:NORTH_AND_OR_SOUTH]
[MINERAL_SCARCITY:2500]
[MEGABEAST_CAP:75]
[SEMIMEGABEAST_CAP:150]
[TITAN_NUMBER:33]
[TITAN_ATTACK_TRIGGER:80:0:100000]
[DEMON_NUMBER:52]
[NIGHT_TROLL_NUMBER:26]
[BOGEYMAN_NUMBER:26]
[VAMPIRE_NUMBER:26]
[WEREBEAST_NUMBER:26]
[SECRET_NUMBER:52]
[REGIONAL_INTERACTION_NUMBER:52]
[DISTURBANCE_INTERACTION_NUMBER:52]
[EVIL_CLOUD_NUMBER:26]
[EVIL_RAIN_NUMBER:26]
[GENERATE_DIVINE_MATERIALS:1]
[GOOD_SQ_COUNTS:24:244:0]
[EVIL_SQ_COUNTS:24:244:0]
[PEAK_NUMBER_MIN:12]
[PARTIAL_OCEAN_EDGE_MIN:0]
[COMPLETE_OCEAN_EDGE_MIN:4]
[VOLCANO_MIN:4]
[REGION_COUNTS:SWAMP:252:1:1]
[REGION_COUNTS:DESERT:252:1:1]
[REGION_COUNTS:FOREST:1008:3:2]
[REGION_COUNTS:MOUNTAINS:2016:2:2]
[REGION_COUNTS:OCEAN:2016:1:1]
[REGION_COUNTS:GLACIER:63:0:0]
[REGION_COUNTS:TUNDRA:126:0:0]
[REGION_COUNTS:GRASSLAND:2016:3:2]
[REGION_COUNTS:HILLS:2016:3:2]
[EROSION_CYCLE_COUNT:250]
[RIVER_MINS:100:100]
[PERIODICALLY_ERODE_EXTREMES:1]
[OROGRAPHIC_PRECIPITATION:1]
[SUBREGION_MAX:3500]
[CAVERN_LAYER_COUNT:3]
[CAVERN_LAYER_OPENNESS_MIN:0]
[CAVERN_LAYER_OPENNESS_MAX:100]
[CAVERN_LAYER_PASSAGE_DENSITY_MIN:0]
[CAVERN_LAYER_PASSAGE_DENSITY_MAX:100]
[CAVERN_LAYER_WATER_MIN:0]
[CAVERN_LAYER_WATER_MAX:100]
[HAVE_BOTTOM_LAYER_1:1]
[HAVE_BOTTOM_LAYER_2:1]
[LEVELS_ABOVE_GROUND:15]
[LEVELS_ABOVE_LAYER_1:5]
[LEVELS_ABOVE_LAYER_2:1]
[LEVELS_ABOVE_LAYER_3:1]
[LEVELS_ABOVE_LAYER_4:1]
[LEVELS_ABOVE_LAYER_5:2]
[LEVELS_AT_BOTTOM:1]
[CAVE_MIN_SIZE:5]
[CAVE_MAX_SIZE:25]
[MOUNTAIN_CAVE_MIN:40]
[NON_MOUNTAIN_CAVE_MIN:60]
[ALL_CAVES_VISIBLE:0]
[SHOW_EMBARK_TUNNEL:2]
[TOTAL_CIV_NUMBER:40]
[TOTAL_CIV_POPULATION:15000]
[SITE_CAP:1500]
[PLAYABLE_CIVILIZATION_REQUIRED:1]
[ELEVATION_RANGES:33000:4032:2016]
[RAIN_RANGES:2016:4032:2016]
[DRAINAGE_RANGES:2016:4032:2016]
[SAVAGERY_RANGES:2016:4032:2016]
[VOLCANISM_RANGES:2016:4032:2016]
Yogas don't have a BIOS setting to toggle hyperthreading but you can turn off cores using;
$ echo 0 > /sys/devices/system/cpu/cpu2/online
$ echo 0 > /sys/devices/system/cpu/cpu3/online
Hyperthreading (off) it 'turboboosts' to 2.7GHz and kept the same temp as before. Right there is was thinking it might be 10% faster but in the end it was about 2mins slower. I ran the Hyperthreading (off) test again and got the same results. Hyperthreading (on) ran the test again and same as before.
Thoughts; possibly only having single channel RAM is a bottleneck. Hyperthreading might allow saving to take less time. The way I shut off the Hyperthreading cores leaves some overhead that causes some slow down a BIOS setting might be better. World gen might not be an accurate method for testing in game FPS gains. It was fun messing around with this even if it didn't help.