Sponsored Content
Operating Systems Solaris Could you run this benchmark? (Especially if you have a V880 or V890) Post 302980161 by MadeInGermany on Wednesday 24th of August 2016 02:39:32 PM
Old 08-24-2016
I have neither a V440 nor a fortran compiler.
But you can get a rough figure by comparing the clock speeds. Note that the Niagara (e.g. the T5 series) uses half the clock speed on the CPU cores. For example a 3.0 GHz Niagara should be like a 1.5 Ghz V440 in computation.
However the Niagara could run more computations (e.g. benchmarks) in parallel with still high speed.
 

9 More Discussions You Might Find Interesting

1. UNIX Benchmarks

Ultra 10 benchmark

CPU/Speed: Ultrasparc IIi / 300MHz Ram: 128MB (Not enough) Motherboard: Sun Ultra 5/10 Bus: 4 PCI Cache: 512K Ecache Controller: Onboard IDE ATA/33 Disk: 40GB IBM ATA/100 Load: Low, 1 user, apache, samba, ipf, dtlogin disabled. Kernel: Solaris 5.10 b72 Kernel ELF?: yes pgms: I used the... (0 Replies)
Discussion started by: 98_1LE
0 Replies

2. UNIX Benchmarks

AMD-K5 Benchmark

AMD-K5 Processor at 133Mhz 32MB RAM 5 GB Hard Drive 10MB NIC 1MB ARC Graphics Card PS/1 Keyboard CD-ROM Floppy Drive Kickin' Fast BABY! hehe BYTE UNIX Benchmarks (Version 3.11) System -- FreeBSD evil-linux.net 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003... (0 Replies)
Discussion started by: Phobos
0 Replies

3. Linux

Benchmark for Linux

I work in a computer company which sells computer configurations and parts of them. And I want to give a choice to customers. If they want to buy a PC with Linux installed, not Windows. But I find difficult to test the Graphic Cards in Linux OS. I have searched the web and I didn't found any... (2 Replies)
Discussion started by: vlatkop
2 Replies

4. Solaris

How to configure my SAN with Sun V880 servers to run Oracle 9i

Hi: I am in the process of configuring the SAN for Solaris to host 6 oracle 9i databases. We have 30 -146 GB disks stiped with RAID 10 for SAN. Of which 11 are dedicated for databsaes related things. Then we have 2 v880 Sun Servers with 16 -73 GB disks and 24 GB memory. The questions... (1 Reply)
Discussion started by: oracle_dba
1 Replies

5. UNIX for Advanced & Expert Users

V890 Benefits over V880

Hello, Need to know all benefits\differences for V890 over V880. We are really keen to know about this. Can anybody please take out some time and get us the information. Regards, Narinder (4 Replies)
Discussion started by: narinderd
4 Replies

6. Solaris

Installing Solaris 8 on a V890

Question, I have a new V890 preloaded witrh Solaris 10. Due to SW compatibility I need to run Sol 8 on the server. When running boot cdrom from the ok prompt, I get amessages looking for a location on the CDROM to find the startup install SW. The path must be different from what's on Sol 10 install... (4 Replies)
Discussion started by: stocksj
4 Replies

7. Solaris

HBA problem...? at SF V890

Dear All, I need your help. I have server like this SunOS 5.10 Generic_141444-09 sun4u sparc SUNW,Sun-Fire-V890 with messages like this... Oct 10 17:07:52 iscsi: NOTICE: unrecognized ioctl 0x403 Oct 10 17:07:52 scsi: WARNING: /pseudo/fcp@0 (fcp0): Oct 10 17:07:52 Invalid... (4 Replies)
Discussion started by: mbah_jiman
4 Replies

8. Solaris

v890 cannot boot

I just received a v890. I cannot get it to boot via CDROM nor can I access the SC prompt because I do not know the password. I am attempting to access it via serial cable to a Linux box. What is the best way to proceed? (25 Replies)
Discussion started by: LittleLebowski
25 Replies

9. Shell Programming and Scripting

Shell Script: Run benchmark and cpustat together

Hello, New to Shell scripting here. :-( I am trying to do the following: - Run a long benchmark program (Don't need to see the outputs to stdout) - As long as the benchmark is running, run the "cpustat" command with one particular Performance Counter. - When the (Multi-thread) benchmark is... (1 Reply)
Discussion started by: Zam_1234
1 Replies
PCAP-TSTAMP(7)						 Miscellaneous Information Manual					    PCAP-TSTAMP(7)

NAME
pcap-tstamp - packet time stamps in libpcap DESCRIPTION
When capturing traffic, each packet is given a time stamp representing, for incoming packets, the arrival time of the packet and, for out- going packets, the transmission time of the packet. This time is an approximation of the arrival or transmission time. If it is supplied by the operating system running on the host on which the capture is being done, there are several reasons why it might not precisely repre- sent the arrival or transmission time: if the time stamp is applied to the packet when the networking stack receives the packet, the networking stack might not see the packet until an interrupt is delivered for the packet or a timer event causes the networking device driver to poll for packets, and the time stamp might not be applied until the packet has had some processing done by other code in the networking stack, so there might be a significant delay between the time when the last bit of the packet is received by the capture device and when the net- working stack time-stamps the packet; the timer used to generate the time stamps might have low resolution, for example, it might be a timer updated once per host operat- ing system timer tick, with the host operating system timer ticking once every few milliseconds; a high-resolution timer might use a counter that runs at a rate dependent on the processor clock speed, and that clock speed might be adjusted upwards or downwards over time and the timer might not be able to compensate for all those adjustments; the host operating system's clock might be adjusted over time to match a time standard to which the host is being synchronized, which might be done by temporarily slowing down or speeding up the clock or by making a single adjustment; different CPU cores on a multi-core or multi-processor system might be running at different speeds, or might not have time counters all synchronized, so packets time-stamped by different cores might not have consistent time stamps. In addition, packets time-stamped by different cores might be time-stamped in one order and added to the queue of packets for libpcap to read in another order, so time stamps might not be monotonically increasing. Some capture devices on some platforms can provide time stamps for packets; those time stamps are usually high-resolution time stamps, and are usually applied to the packet when the first or last bit of the packet arrives, and are thus more accurate than time stamps provided by the host operating system. Those time stamps might not, however, be synchronized with the host operating system's clock, so that, for example, the time stamp of a packet might not correspond to the time stamp of an event on the host triggered by the arrival of that packet. Depending on the capture device and the software on the host, libpcap might allow different types of time stamp to be used. The pcap_list_tstamp_types(3PCAP) routine provides, for a packet capture handle created by pcap_create(3PCAP) but not yet activated by pcap_activate(3PCAP), a list of time stamp types supported by the capture device for that handle. The list might be empty, in which case no choice of time stamp type is offered for that capture device. If the list is not empty, the pcap_set_tstamp_type(3PCAP) routine can be used after a pcap_create() call and before a pcap_activate() call to specify the type of time stamp to be used on the device. The time stamp types are listed here; the first value is the #define to use in code, the second value is the value returned by pcap_tstamp_type_val_to_name() and accepted by pcap_tstamp_name_to_val(). PCAP_TSTAMP_HOST - host Time stamp provided by the host on which the capture is being done. The precision of this time stamp is unspecified; it might or might not be synchronized with the host operating system's clock. PCAP_TSTAMP_HOST_LOWPREC - host_lowprec Time stamp provided by the host on which the capture is being done. This is a low-precision time stamp, synchronized with the host operating system's clock. PCAP_TSTAMP_HOST_HIPREC - host_hiprec Time stamp provided by the host on which the capture is being done. This is a high-precision time stamp; it might or might not be synchronized with the host operating system's clock. It might be more expensive to fetch than PCAP_TSTAMP_HOST_LOWPREC. PCAP_TSTAMP_ADAPTER - adapter Time stamp provided by the network adapter on which the capture is being done. This is a high-precision time stamp, synchronized with the host operating system's clock. PCAP_TSTAMP_ADAPTER_UNSYNCED - adapter_unsynced Time stamp provided by the network adapter on which the capture is being done. This is a high-precision time stamp; it is not synchronized with the host operating system's clock. SEE ALSO
pcap_set_tstamp_type(3PCAP), pcap_list_tstamp_types(3PCAP), pcap_tstamp_type_val_to_name(3PCAP), pcap_tstamp_name_to_val(3PCAP) 22 August 2010 PCAP-TSTAMP(7)
All times are GMT -4. The time now is 05:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy