[opensuse-buildservice] Some questions about buildservice.
Hello, Some Questions. - Is it possible to use a few ioDrive PCIe Solid State Memory cards [ 80 ,160 or 320GB cards ] [1] to handle big obs build jobs ,speed-up build service. e.g kernel, java, libreoffice factory builds. - Also is it possible to use ioDrive with x86_64 pre-built image to copy as build for big build jobs. - Be interesting with just 1 card and say how many packages it builds in a day [keep stats about these details] --Glenn [1] price list ioDrive PCIe Solid State Memory cards ebay [ lists 80 ,160 32 and 640GB cards] http://www.ebay.com/sch/Computers-Tablets-Networking-/58058/i.html?_from=R40&_nkw=iodrive&_sop=15 [2] Fusion IO Interview https://www.youtube.com/watch?v=PgQcpPEu36I [3]About (from url) http://www.solidstateworks.com.au/ioDrive.asp?gclid=CM2ZwtCmwMQCFdcRvQodhIwA... Unparalleled Performance Density The ioDrive is a revolutionary new solid state technology that dramatically increases bandwidth and application performance, reduces latency, and simplifies your IT infrastructure, all while slashing capital and operating costs. Fusion's ioDrive dramatically improves application response times with a persistent, high-performance, high-capacity ioMemory tier. It enables data decentralized architectures that move terabytes of process-critical data into servers. This minimizes application latency to deliver groundbreaking improvements to computing performance, while greatly reducing hardware infrastructure, maintenance, floor space, and energy costs. Minimizes latency and eliminates I/O bottlenecks by integrating with host servers as a memory tier extension. Accelerating Your Data Integrates with servers at the system bus and kernel level, creating a new Flash memory tier Not an Solid State Disk (SSD) - easily outperforms dozens of SSDs and a single server Accelerates applications, improves response times, and boosts efficiency Reduces storage latencies and eliminates I/O bottlenecks Delivers the performance of thousands of disk drives in a single server From 160GB - 640GB of enterprise-grade, solid-state Flash Easy to use, highly reliable -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 24. März 2015, 17:48:18 wrote doiggl@velocitynet.com.au:
Hello, Some Questions.
- Is it possible to use a few ioDrive PCIe Solid State Memory cards [ 80 ,160 or 320GB cards ] [1] to handle big obs build jobs ,speed-up build service.
sure, but we have not tried yet.
e.g kernel, java, libreoffice factory builds.
- Also is it possible to use ioDrive with x86_64 pre-built image to copy as build for big build jobs.
what should be different when usibg them? pre-built images have little impact on big build jobs though. They are more helpfull, when the install time makes a significant amount of time of the build job.
- Be interesting with just 1 card and say how many packages it builds in a day [keep stats about these details]
feel free to try it. However, flash memory might die earlier then usual, since OBS workers do really write a lot of data...
--Glenn
[1] price list ioDrive PCIe Solid State Memory cards ebay [ lists 80 ,160 32 and 640GB cards] http://www.ebay.com/sch/Computers-Tablets-Networking-/58058/i.html?_from=R40&_nkw=iodrive&_sop=15
[2] Fusion IO Interview https://www.youtube.com/watch?v=PgQcpPEu36I
[3]About (from url) http://www.solidstateworks.com.au/ioDrive.asp?gclid=CM2ZwtCmwMQCFdcRvQodhIwA...
Unparalleled Performance Density
The ioDrive is a revolutionary new solid state technology that dramatically increases bandwidth and application performance, reduces latency, and simplifies your IT infrastructure, all while slashing capital and operating costs.
Fusion's ioDrive dramatically improves application response times with a persistent, high-performance, high-capacity ioMemory tier. It enables data decentralized architectures that move terabytes of process-critical data into servers. This minimizes application latency to deliver groundbreaking improvements to computing performance, while greatly reducing hardware infrastructure, maintenance, floor space, and energy costs. Minimizes latency and eliminates I/O bottlenecks by integrating with host servers as a memory tier extension.
Accelerating Your Data
Integrates with servers at the system bus and kernel level, creating a new Flash memory tier Not an Solid State Disk (SSD) - easily outperforms dozens of SSDs and a single server Accelerates applications, improves response times, and boosts efficiency Reduces storage latencies and eliminates I/O bottlenecks Delivers the performance of thousands of disk drives in a single server From 160GB - 640GB of enterprise-grade, solid-state Flash Easy to use, highly reliable
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 2015-03-24 07:48, doiggl@velocitynet.com.au wrote:
Hello, Some Questions.
- Is it possible to use a few ioDrive PCIe Solid State Memory cards [ 80 ,160 or 320GB cards ] [1] to handle big obs build jobs ,speed-up build service.
There's no point in bringing this up repeatedly. http://lists.opensuse.org/opensuse-buildservice/2012-09/msg00002.html -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi How do I include some (libstdc++.i686 and libgcc.i686) as BuildRequires... I have tried to add them as BuildRequires: libgcc.i686, libstdc++.i686 BuildRequires: libgcc()(32bit), libstdc++()(32bit) BuildRequires: /lib/libgcc_s.so.1, /lib/ld-linux.so.2 But all of the above, fails to resolve dependencies... What to do?? Thanks Martin Juhl -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Montag, 13. April 2015, 09:49:22 wrote Martin Juhl:
Hi
How do I include some (libstdc++.i686 and libgcc.i686) as BuildRequires...
I have tried to add them as
BuildRequires: libgcc.i686, libstdc++.i686 BuildRequires: libgcc()(32bit), libstdc++()(32bit) BuildRequires: /lib/libgcc_s.so.1, /lib/ld-linux.so.2
But all of the above, fails to resolve dependencies...
What to do??
This depends heavily on the distribution, do you ask for (open)SUSE distros? libstdc++6-32bit should pull it in here. However, usually we do only build in 32bit environements and export it to 64bit afterwards using our baselibs wrapper. Can you describe a bit more detailed why do you want to use 32bit libs in 64bit at all? Usually you can not compile against them there... -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi
Sorry for not specifying distro.. This is on RHEL6...
I'm trying to repackage a tar.gz installer into a rpm-file...
In this installer, some of the installers internal java is 32-bit and some are 64-bit... (IBM-stuff)...
So I need the 32-bit libraries to be able to run the installer...
It seems like:
BuildRequires: libgcc(x86-32), libstdc++(x86-32)
Should be the correct way to do this, and is also accepted if I do a 32-bit build.. but not if I try to do a 64-bit build...
Regards
Martin
----- Original meddelelse -----
Fra: "Adrian Schröter"
Hi
How do I include some (libstdc++.i686 and libgcc.i686) as BuildRequires...
I have tried to add them as
BuildRequires: libgcc.i686, libstdc++.i686 BuildRequires: libgcc()(32bit), libstdc++()(32bit) BuildRequires: /lib/libgcc_s.so.1, /lib/ld-linux.so.2
But all of the above, fails to resolve dependencies...
What to do??
This depends heavily on the distribution, do you ask for (open)SUSE distros? libstdc++6-32bit should pull it in here. However, usually we do only build in 32bit environements and export it to 64bit afterwards using our baselibs wrapper. Can you describe a bit more detailed why do you want to use 32bit libs in 64bit at all? Usually you can not compile against them there... -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Adrian Schröter
-
doiggl@velocitynet.com.au
-
Jan Engelhardt
-
Martin Juhl