When opening first time,application take long time.

[Quonsal]

When I open new application after log in like Firefox,libreoffice,software manager or any thing else,they take long time to open.But after opening first time whenever I open those application again they open very fast.How to make open app faster first time.I have used prelink,preload.But I didn't find any difference.

[Hoser Rob]

I don't know what you mean by slow exactly. But when you load an app and then close it and open it later it does load faster. That's because Linux, unlike WIndows, doesn't just leave RAM unused by apps just sitting there. It uses it for caching app software. So the next time you open it it's loaded straight from RAM instead of disk,

Preload isn't a substitute for this caching, and it doesn't work well for all apps. Have a look at this ..

https://askubuntu.com/questions/110335/ ... by-default

[Quonsal]

It takes about a minute.Is there no way to start it up in seconds after log in.
Processor: i5-6200U
RAM:8GB DDR4
HARD DRIVE:1TB HDD.
Why does it take this time and how to reduce it?
Is there any os which can load an app faster than Linux mint?

[JerryF]

It takes about a minute.Is there no way to start it up in seconds after log in.
Processor: i5-6200U
RAM:8GB DDR4
HARD DRIVE:1TB HDD.
Why does it take this time and how to reduce it?
Is there any os which can load an app faster than Linux mint?

I have the same situation on my HP laptop. When I click on an app that I have in the panel, it "pulsates" about 3 times and then takes about 10 to 15 seconds to open, then after that first time if I close and open the app, it opens immediately.

Unfortunately, I haven't found a solution. If I had, I would have given it to you.

Strangely, I don't have this situation in my VirtualBox that is set up with 2GB RAM, 64MB display using my work computer.

[Quonsal]

If virtual box don't​ face this problem than what is the reason behind that?
Can any one suggest me os which can load faster an application after log in?

[JerryF]

If virtual box don't​ face this problem than what is the reason behind that?

I haven't a clue.

[Quonsal]

Can any one suggest me os which can load faster an application after log in?

[Hoser Rob]

Mint isn't particuarly slow at loading apps. Will the OP please generate a detailed system report ... copy/paste this into the terminal and copy/paste the text output here:

Code: Select all

inxi -Fxz

[Quonsal]

Code: Select all

System:    Host: QUONSAL Kernel: 4.10.0-26-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.4.4 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.2 Sonya
Machine:   System: LENOVO (portable) product: 80SM v: Lenovo ideapad 310-15ISK
           Mobo: LENOVO model: Toronto 5A2 v: NO DPK
           Bios: LENOVO v: 0XCN40WW date: 03/02/2017
CPU:       Dual core Intel Core i5-6200U (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9600
           clock speeds: max: 2800 MHz 1: 499 MHz 2: 499 MHz 3: 499 MHz
           4: 499 MHz
Graphics:  Card-1: Intel Sky Lake Integrated Graphics bus-ID: 00:02.0
           Card-2: NVIDIA Device 134f bus-ID: 03:00.0
           Display Server: X.Org 1.18.4 driver: nvidia
           Resolution: 1366x768@59.97hz
           GLX Renderer: GeForce 920MX/PCIe/SSE2
           GLX Version: 4.5.0 NVIDIA 375.66 Direct Rendering: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio
           driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.10.0-26-generic
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus-ID: 01:00.0
           IF: enp1s0 state: down mac: <filter>
           Card-2: Intel Intel Dual Band Wireless-AC 3165 Plus Bluetooth
           driver: iwlwifi bus-ID: 02:00.0
           IF: wlp2s0 state: up mac: <filter>
Drives:    HDD Total Size: 1000.2GB (9.7% used)
           ID-1: /dev/sda model: WDC_WD10JPCX size: 1000.2GB
Partition: ID-1: / size: 908G used: 83G (10%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 8.49GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 43.0C mobo: N/A gpu: 0.0:39C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 219 Uptime: 1 min Memory: 845.1/7888.1MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35

[Quonsal]

Pls do the needful and try to solve this as early as possible.Have you got any mistake or it is normal?

[JerryF]

Pls do the needful and try to solve this as early as possible.Have you got any mistake or it is normal?

Rushing members is not going to help any more than not rushing them.

[Quonsal]

Pls do the needful and try to solve this as early as possible.Have you got any mistake or it is normal?

Rushing members is not going to help any more than not rushing them.

I didn't understand

[Mute Ant]

Slow-the-first-time suggests the OS is fine, your disk drive is causing the problem, and yes that's normal. You can reduce drive access times by keeping the OS in a partition significantly smaller than the total (called short-stroking) or using a fast silicon store for the OS.

I use a 27GB partition of a 500GB drive...firefox takes less than 15 seconds to start first time, less than 5 seconds once it's cached in RAM.

"Pls do the needful and try to solve this as early as possible." You would have to demonstrate a reproducible defect (whisper 'bug') in the software for it to be changed. All we can do here is try to get your system running like ours.

[Quonsal]

Slow-the-first-time suggests the OS is fine, your disk drive is causing the problem, and yes that's normal. You can reduce drive access times by keeping the OS in a partition significantly smaller than the total (called short-stroking) or using a fast silicon store for the OS.

I use a 27GB partition of a 500GB drive...firefox takes less than 15 seconds to start first time, less than 5 seconds once it's cached in RAM.

"Pls do the needful and try to solve this as early as possible." You would have to demonstrate a reproducible defect (whisper 'bug') in the software for it to be changed. All we can do here is try to get your system running like ours.

I don't know how to do short-stroking.Can it reduce time of opening an application remarkably?
Has anyone experienced difference?
If,yes.Then show me how to do that.

[Mute Ant]

"I don't know how to do short-stroking." You install your OS to a small partition near the start of the drive, or shrink your OS partition to 'small'...10% of the total is about right. Files in a 100GB sda1 at the start of a 1000GB drive will be reached ~10x faster and read ~2x faster.

https://en.wikipedia.org/wiki/Hard_disk ... cteristics
Note the graphic...
https://en.wikipedia.org/wiki/Hard_disk ... _Disks.png
...their drive's fast end is 147.9MB/s and the slow end 62.5MB/s...that's normal HDD performance. That's why Windows 'defrag' programs move everything to the start of the drive.

http://www.tomshardware.com/reviews/sho ... 157-2.html Interesting experimental report. Complicated 'results' tables.

"Can it reduce time of opening an application remarkably?" Yes.

"Has anyone experienced difference?" Yes.

"Then show me how to do that."
o Back-up your system (or practice on something disposable)
o Boot a Live Session Mint, or a gPartedLive CD.
o Shrink your OS partition to the larger of...
oo Smallest possible +20%
oo 20 GiB == 20480 MiB
oo 10% of the total drive

[austin.texas]

Install your OS on a SSD instead of a mechanical hard drive.
If you install the OS on one hard drive, and the /home directory on a different hard drive, it will reduce the seek time, and load some programs faster.

[Quonsal]

Install your OS on a SSD instead of a mechanical hard drive.
If you install the OS on one hard drive, and the /home directory on a different hard drive, it will reduce the seek time, and load some programs faster.

Thanks.I know that an SSD will absolutely reduce seek time but I haven't an SSD.

[Mute Ant]

I will add the thought that a slow-reading hard drive, which you appear to have, might be in the early throes of a re-re-re-re-read failure, where weakly-recorded data causes the drive's firmware to pause on every track, waiting for a good copy of the block it is looking for. The Disks accessory will do a read-only benchmark test for you, it should look like the graphic I linked to.