Comments on: Pier and GLASS on Slicehost http://gemstonesoup.wordpress.com/2008/10/21/pier-and-glass-on-slicehost/ tips and techniques for using GemStone/S and Seaside Fri, 06 Nov 2009 22:54:49 +0000 http://wordpress.com/ hourly 1 By: Pier Programming « (gem)Stone Soup http://gemstonesoup.wordpress.com/2008/10/21/pier-and-glass-on-slicehost/#comment-1295 Pier Programming « (gem)Stone Soup Sun, 02 Nov 2008 05:24:16 +0000 http://gemstonesoup.wordpress.com/?p=738#comment-1295 [...] post where I’m recording my experiences using Pier and GLASS for wife’s website. In the first post, I got GLASS and Pier installed on Slicehost using lighttpd as the web [...] [...] post where I’m recording my experiences using Pier and GLASS for wife’s website. In the first post, I got GLASS and Pier installed on Slicehost using lighttpd as the web [...]

]]> By: Dale Henrichs http://gemstonesoup.wordpress.com/2008/10/21/pier-and-glass-on-slicehost/#comment-1285 Dale Henrichs Sat, 25 Oct 2008 22:30:42 +0000 http://gemstonesoup.wordpress.com/?p=738#comment-1285 Hey Pete, The cpu mapping is done at the OS level (inside the Xen server instance) so from inside the Xen instance on your Slicehost you can't tell what physical cpu mapping is being used. As far as GemStone (and the OS) is concerned you are running on core #1... Hey Pete,

The cpu mapping is done at the OS level (inside the Xen server instance) so from inside the Xen instance on your Slicehost you can’t tell what physical cpu mapping is being used. As far as GemStone (and the OS) is concerned you are running on core #1…

]]> By: pete http://gemstonesoup.wordpress.com/2008/10/21/pier-and-glass-on-slicehost/#comment-1284 pete Sat, 25 Oct 2008 21:47:17 +0000 http://gemstonesoup.wordpress.com/?p=738#comment-1284 Could you clarify something for me? I believe GLASS (free) is configured to always run on the 1st core in a multi-core setup. How does this work in a slicehost environment e.g. could it happen that your slice is given core # 2 ? Thanks. Could you clarify something for me? I believe GLASS (free) is configured to always run on the 1st core in a multi-core setup. How does this work in a slicehost environment e.g. could it happen that your slice is given core # 2 ?

Thanks.

]]>