Slow JumpStart on a Sun Fire V240 - Revision history

Hutch at 15:41, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:41:55 GMT

←Older revision		Revision as of 15:41, 16 October 2007
Line 3:		Line 3:
	I noticed two problems:		I noticed two problems:

-	* The ''sysidcfg'' file specified DNS name service, but the DNS server was unreachable. This '''~~really~~''' slowed down JumpStart. The time server was also unreachable (although it shouldn't affect JumpStart speed), so I put the following in ''sysidcfg'':	+	* The ''sysidcfg'' file specified DNS name service, but the DNS server was unreachable. This '''significantly''' slowed down JumpStart. The time server was also unreachable (although it shouldn't affect JumpStart speed), so I put the following in ''sysidcfg'':
	name_service=NONE		name_service=NONE
	timeserver=localhost		timeserver=localhost

Hutch at 15:37, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:37:48 GMT

←Older revision		Revision as of 15:37, 16 October 2007
Line 47:		Line 47:
	1		1

-	Although the main reason for the slow JumpStart build was ~~problems reaching~~ the DNS server, forcing the ''bge'' interface to 100 Mbit may also have improved the build speed.	+	Although the main reason for the slow JumpStart build was that the DNS server in ''sysidcfg'' was unreachable, forcing the ''bge'' interface to 100 Mbit may also have improved the build speed.

Hutch at 15:36, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:36:54 GMT

←Older revision		Revision as of 15:36, 16 October 2007
Line 47:		Line 47:
	1		1

-	Although ~~problems reaching the specified DNS server was~~ the main reason for the slow JumpStart build, forcing the ''bge'' interface to 100 Mbit may also have improved the build speed.	+	Although the main reason for the slow JumpStart build was problems reaching the DNS server, forcing the ''bge'' interface to 100 Mbit may also have improved the build speed.

Hutch at 15:36, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:36:15 GMT

←Older revision		Revision as of 15:36, 16 October 2007
Line 35:		Line 35:
	(I don't know if the ''sleep'' command above is needed, but when I didn't have it, ''link_speed'' immediately returned 0, and ''link_duplex'' immediately returned -1)		(I don't know if the ''sleep'' command above is needed, but when I didn't have it, ''link_speed'' immediately returned 0, and ''link_duplex'' immediately returned -1)

-	Since the switch and the OS are set to autonegotiate, the interface falls back to 100 Mbit.	+	Since the switch and the OS are set to autonegotiate, the interface falls back to 100 Mbit:

	Current /dev/bge0 link_speed:		Current /dev/bge0 link_speed:
Line 47:		Line 47:
	1		1

-	Although ~~the inability of the JumpStart client to reach~~ the specified DNS server was the main ~~cause of~~ the ~~problems~~, forcing the ''bge'' interface to 100 Mbit may also have improved the build speed.	+	Although problems reaching the specified DNS server was the main reason for the slow JumpStart build, forcing the ''bge'' interface to 100 Mbit may also have improved the build speed.

Hutch at 15:34, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:34:57 GMT

←Older revision		Revision as of 15:34, 16 October 2007
Line 12:		Line 12:
	100 Mbit: 2-3 seconds		100 Mbit: 2-3 seconds

-	To force 100 Mbit during the JumpStart, I created a ''Begin'' script that ~~disables~~ the 1000 Mbit capability	+	To force 100 Mbit during the JumpStart, I created a ''Begin'' script that disabled the 1000 Mbit capability.

	#!/bin/sh		#!/bin/sh

Hutch at 15:34, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:34:39 GMT

←Older revision		Revision as of 15:34, 16 October 2007
Line 12:		Line 12:
	100 Mbit: 2-3 seconds		100 Mbit: 2-3 seconds

-	To force 100 Mbit during the JumpStart, I created a ''Begin'' script that disables the 1000 Mbit capability~~. Although you can apparently do a ''boot ...:speed=100,duplex=full'' on ''ce'' interfaces[http://www.sun.com/blueprints/0704/817-7526.pdf], it didn't seem to work on the ''bge'' interface.~~	+	To force 100 Mbit during the JumpStart, I created a ''Begin'' script that disables the 1000 Mbit capability

	#!/bin/sh		#!/bin/sh

Hutch at 15:33, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:33:08 GMT

←Older revision		Revision as of 15:33, 16 October 2007
Line 12:		Line 12:
	100 Mbit: 2-3 seconds		100 Mbit: 2-3 seconds

-	I created a ''Begin'' script that disables the 1000 Mbit capability. Although you can apparently do a ''boot ...:speed=100,duplex=full'' on ''ce'' interfaces[http://www.sun.com/blueprints/0704/817-7526.pdf], it didn't seem to work on the ''bge'' interface.	+	To force 100 Mbit during the JumpStart, I created a ''Begin'' script that disables the 1000 Mbit capability. Although you can apparently do a ''boot ...:speed=100,duplex=full'' on ''ce'' interfaces[http://www.sun.com/blueprints/0704/817-7526.pdf], it didn't seem to work on the ''bge'' interface.

	#!/bin/sh		#!/bin/sh

Hutch at 15:32, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:32:40 GMT

←Older revision		Revision as of 15:32, 16 October 2007
Line 7:		Line 7:
	timeserver=localhost		timeserver=localhost

-	* 100 Mbit transfers were 3-4x faster than 1000 Mbit between the JumpStart client and JumpStart server. I did a ''boot net -s'' and copied a ~120 MB directory from the JumpStart server.	+	* 100 Mbit transfers were 3-4x faster than 1000 Mbit between the JumpStart client and JumpStart server. I did a ''boot net -s'' and copied a ~120 MB directory from the JumpStart server:

	1000 Mbit: 10-12 seconds		1000 Mbit: 10-12 seconds

Hutch at 15:32, 16 October 2007

Hutch — Tue, 16 Oct 2007 15:32:16 GMT

←Older revision		Revision as of 15:32, 16 October 2007
Line 3:		Line 3:
	I noticed two problems:		I noticed two problems:

-	* The ''sysidcfg'' file specified DNS name service, but the DNS server is unreachable. This '''really''' ~~slow~~ down JumpStart. The time server was also unreachable (although it shouldn't affect JumpStart speed), so I put the following in ''sysidcfg'':	+	* The ''sysidcfg'' file specified DNS name service, but the DNS server was unreachable. This '''really''' slowed down JumpStart. The time server was also unreachable (although it shouldn't affect JumpStart speed), so I put the following in ''sysidcfg'':
	name_service=NONE		name_service=NONE
	timeserver=localhost		timeserver=localhost

Hutch: New page: I was asked to investigate a slow custom JumpStart build over gigabit ethernet on a Sun Fire V240. Apparently, packages were installing at the rate of 40 MB/hour. I noticed two problems: ...

Hutch — Tue, 16 Oct 2007 15:31:18 GMT

New page: I was asked to investigate a slow custom JumpStart build over gigabit ethernet on a Sun Fire V240. Apparently, packages were installing at the rate of 40 MB/hour. I noticed two problems: ...

New page

I was asked to investigate a slow custom JumpStart build over gigabit ethernet on a Sun Fire V240. Apparently, packages were installing at the rate of 40 MB/hour.

I noticed two problems:

* The ''sysidcfg'' file specified DNS name service, but the DNS server is unreachable. This '''really''' slow down JumpStart. The time server was also unreachable (although it shouldn't affect JumpStart speed), so I put the following in ''sysidcfg'':
name_service=NONE
timeserver=localhost

* 100 Mbit transfers were 3-4x faster than 1000 Mbit between the JumpStart client and JumpStart server. I did a ''boot net -s'' and copied a ~120 MB directory from the JumpStart server.

1000 Mbit: 10-12 seconds
100 Mbit: 2-3 seconds

I created a ''Begin'' script that disables the 1000 Mbit capability. Although you can apparently do a ''boot ...:speed=100,duplex=full'' on ''ce'' interfaces[http://www.sun.com/blueprints/0704/817-7526.pdf], it didn't seem to work on the ''bge'' interface.

#!/bin/sh

echo "Current /dev/bge0 link_speed:"
ndd -get /dev/bge0 link_speed
echo "Current /dev/bge0 link_duplex:"
ndd -get /dev/bge0 link_duplex

ndd -set /dev/bge0 adv_1000fdx_cap 0
# Not needed
ndd -set /dev/bge0 adv_1000hdx_cap 0

echo "Sleeping 10 seconds..."
sleep 10

echo "New /dev/bge0 link_speed:"
ndd -get /dev/bge0 link_speed
echo "New /dev/bge0 link_duplex:"
ndd -get /dev/bge0 link_duplex

(I don't know if the ''sleep'' command above is needed, but when I didn't have it, ''link_speed'' immediately returned 0, and ''link_duplex'' immediately returned -1)

Since the switch and the OS are set to autonegotiate, the interface falls back to 100 Mbit.

Current /dev/bge0 link_speed:
1000
Current /dev/bge0 link_duplex:
1
Sleeping 10 seconds...
New /dev/bge0 link_speed:
100
New /dev/bge0 link_duplex:
1

Although the inability of the JumpStart client to reach the specified DNS server was the main cause of the problems, forcing the ''bge'' interface to 100 Mbit may also have improved the build speed.