Startup - Revision history

JaroslavTulach: /* Multi User Initial Launch */

JaroslavTulach — Fri, 19 Sep 2025 15:54:08 GMT

Multi User Initial Launch

←Older revision		Revision as of 15:54, 19 September 2025
Line 73:		Line 73:
	== Multi User Initial Launch ==		== Multi User Initial Launch ==

-	First deviation from the most common workflow is multi user setup. One administrator ~~install~~ your application and then many users	+	First deviation from the most common workflow is multi user setup. One administrator installs your application and then many users
	are going to use it. Only the administrator is going to have the pleasure of ''post-install initial lauch'' (if at all), every		are going to use it. Only the administrator is going to have the pleasure of ''post-install initial lauch'' (if at all), every
	other user is out of luck. For them, the first start happens after booting computer, without any special setup made before that.		other user is out of luck. For them, the first start happens after booting computer, without any special setup made before that.

82.95.54.106 at 11:24, 22 July 2010

82.95.54.106 — Thu, 22 Jul 2010 11:24:45 GMT

←Older revision		Revision as of 11:24, 22 July 2010
Line 1:		Line 1:
-	~~The first encounter is the most important~~. This is old observation valid in many	+	First impressions are very hard to change. This old observation is valid in many
-	fields of human behavior. It is ~~valid~~ also in software development. The	+	fields of human behavior. It is also valid in software development. The
-	first impression ~~is the strongest~~. Make sure your programs behave so that users	+	first impression can be decisive. Make sure your programs behave so that users
-	don't ~~have to~~ think: ''ooh, so broken'', or ''ooh, so slow''.	+	don't think: ''ooh, so broken'', or ''ooh, so slow''.

-	In case of desktop applications, executed on users' own computers, one of the first	+	In the case of desktop applications, executed on users' own computers, one of the first
	impressiond is the time it takes to launch the application. Especially in case of		impressiond is the time it takes to launch the application. Especially in case of
	[[Java]] applications this may be significant - it takes time to load all the		[[Java]] applications this may be significant - it takes time to load all the

217.6.251.18: /* Multi User Initial Launch */

217.6.251.18 — Thu, 22 Jul 2010 07:13:26 GMT

Multi User Initial Launch

←Older revision		Revision as of 07:13, 22 July 2010
Line 74:		Line 74:

	First deviation from the most common workflow is multi user setup. One administrator install your application and then many users		First deviation from the most common workflow is multi user setup. One administrator install your application and then many users
-	are ~~goint~~ to use it. Only the administrator is going to have the pleasure of ''post-install initial lauch'' (if at all), every	+	are going to use it. Only the administrator is going to have the pleasure of ''post-install initial lauch'' (if at all), every
	other user is out of luck. For them, the first start happens after booting computer, without any special setup made before that.		other user is out of luck. For them, the first start happens after booting computer, without any special setup made before that.

JaroslavTulach at 07:57, 18 July 2010

JaroslavTulach — Sun, 18 Jul 2010 07:57:31 GMT

←Older revision		Revision as of 07:57, 18 July 2010
Line 87:		Line 87:

	[[Performance]] conclusion: Make sure significant configuration changes are rare.		[[Performance]] conclusion: Make sure significant configuration changes are rare.
		+
		+	[[Category:APIDesignPatterns:Performance]]

JaroslavTulach: /* Morning Launch */

JaroslavTulach — Sun, 18 Jul 2010 06:55:17 GMT

Morning Launch

←Older revision		Revision as of 06:55, 18 July 2010
Line 64:		Line 64:
	[[Performance]] point of view: This is the most important usecase. Most of the people do this daily and this is their initial		[[Performance]] point of view: This is the most important usecase. Most of the people do this daily and this is their initial
	daily experience. Optimize for this.		daily experience. Optimize for this.
		+
		+
		+	Hint: There is a way to [http://www.linuxinsight.com/proc_sys_vm_drop_caches.html drop filesystem caches] without restart on [[Linux]]:
		+	<source lang="bash">
		+	$ echo 3 > /proc/sys/vm/drop_caches
		+	</source>

	== Multi User Initial Launch ==		== Multi User Initial Launch ==

JaroslavTulach: /* Multi User Initial Launch */

JaroslavTulach — Sun, 18 Jul 2010 06:48:29 GMT

Multi User Initial Launch

←Older revision		Revision as of 06:48, 18 July 2010
Line 71:		Line 71:
	other user is out of luck. For them, the first start happens after booting computer, without any special setup made before that.		other user is out of luck. For them, the first start happens after booting computer, without any special setup made before that.

-	[[Performance]] dilema: Optimize for this case or not? [[NetBeans~~]] [[~~Performance]] team has given up on this usecase in a hope	+	[[Performance]] dilema: Optimize for this case or not? [[NetBeans:Performance]] team has given up on this usecase in a hope
	that this happens just once (not every morning) and only in multiuser setups (which is not a majority).		that this happens just once (not every morning) and only in multiuser setups (which is not a majority).

JaroslavTulach: /* Morning Launch */

JaroslavTulach — Sun, 18 Jul 2010 06:40:42 GMT

Morning Launch

←Older revision		Revision as of 06:40, 18 July 2010
Line 60:		Line 60:
	Our experience with [[NetBeans]] IDE shows that the I/O disk access was really significant factor in ~1min [[startup]] time		Our experience with [[NetBeans]] IDE shows that the I/O disk access was really significant factor in ~1min [[startup]] time
	of [[NetBeans]] IDE 6.0. When we addressed it by using single file start caches, we managed to get to ~20s after few releases.		of [[NetBeans]] IDE 6.0. When we addressed it by using single file start caches, we managed to get to ~20s after few releases.
-	Such time is definitely much ~~better~~ acceptable than original one.	+	Such time is definitely much more acceptable than original one.

	[[Performance]] point of view: This is the most important usecase. Most of the people do this daily and this is their initial		[[Performance]] point of view: This is the most important usecase. Most of the people do this daily and this is their initial

JaroslavTulach: /* Morning Launch */

JaroslavTulach — Sun, 18 Jul 2010 06:39:10 GMT

Morning Launch

←Older revision		Revision as of 06:39, 18 July 2010
Line 46:		Line 46:
	== Morning Launch ==		== Morning Launch ==

-	There are two kinds of desktop applications. Major and minor. A minor application is the one that the user launches,	+	There are two kinds of desktop applications. ''Major'' and ''minor''. A minor application is the one that the user launches,
	performs some operation and exits. An example of this kind is calculator. A major application on the other hand is		performs some operation and exits. An example of this kind is calculator. A major application on the other hand is
	started by the user as soon as the computer is started and it remains on until the computer is powered down. Email client,		started by the user as soon as the computer is started and it remains on until the computer is powered down. Email client,
	[[NetBeans]] (and any other) IDE, or often a web browser falls into this category.		[[NetBeans]] (and any other) IDE, or often a web browser falls into this category.

-	Lauching ''minor'' applications is very similar to the above described ''restart'' case. Most of the libraries is cached,	+	Lauching ''minor'' applications is very similar to the above described ''restart'' case. Most of the libraries are cached,
	the I/O load is not heavy, moreover such applications are likely small. Usually [[performance]] is not an issue.		the I/O load is not heavy, moreover such applications are likely small. Usually [[performance]] is not an issue.

JaroslavTulach: /* Morning Launch */

JaroslavTulach — Sun, 18 Jul 2010 06:38:14 GMT

Morning Launch

←Older revision		Revision as of 06:38, 18 July 2010
Line 48:		Line 48:
	There are two kinds of desktop applications. Major and minor. A minor application is the one that the user launches,		There are two kinds of desktop applications. Major and minor. A minor application is the one that the user launches,
	performs some operation and exits. An example of this kind is calculator. A major application on the other hand is		performs some operation and exits. An example of this kind is calculator. A major application on the other hand is
-	started by the user as soon as the computer is started and it remains on until it is ~~switches off~~. Email client,	+	started by the user as soon as the computer is started and it remains on until the computer is powered down. Email client,
	[[NetBeans]] (and any other) IDE, or often a web browser falls into this category.		[[NetBeans]] (and any other) IDE, or often a web browser falls into this category.

JaroslavTulach: /* Post-install Initial Launch */

JaroslavTulach — Sun, 18 Jul 2010 06:33:39 GMT

Post-install Initial Launch

←Older revision		Revision as of 06:33, 18 July 2010
Line 29:		Line 29:
	be installed. Obviously, the installation needs to be smooth (but that is a topic for another analysis),		be installed. Obviously, the installation needs to be smooth (but that is a topic for another analysis),
	however it does not have to be fast. Case studies show that users are used to wait for installation to finish		however it does not have to be fast. Case studies show that users are used to wait for installation to finish
-	and are ready to accept it ~~to take~~ some time (there is a rummor that Apple, the leading innovator in user interface	+	and are ready to accept if it takes some time (there is a rummor that [[Apple]], the leading innovator in user interface
	design, does disk de-fragmentation as part of install of any application; disk de-fragmentation is completely		design, does disk de-fragmentation as part of install of any application; disk de-fragmentation is completely
	independent task, yet doing it as part of installation is more acceptable for users than running it once per 27 reboots		independent task, yet doing it as part of installation is more acceptable for users than running it once per 27 reboots