Just some thoughts- I hope we can help you resolve this. But I'm guessing one needs to first determine if the OS is right- that things are running at 2.7 Ghz and there is a BIOS setting or something else that is necessary, or that the OS is wrong- in which case the question becomes "why"?
The fact that LINPACK 2.1.2 agrees isn't really meaningful, since as I say we just take the /proc/cpuinfo value when encounter a problem.Īs to the best way to follow-up on this, perhaps someone else out there knows something about this OS distribution? It seems unlikely that you'd be the only one to encounter this problem. The real problem is why does the OS think that your frequency is 2.7GHz? I'm afraid I don't know that answer. So, one might argue that you could use a version of LINPACK that ignores the /proc/cpuinfo frequency however, it seems to me that this is just skipping over a problem and not really fixing it. You see, we have several checks to ensure we get the frequency right in this version of LINPACK, and if it turns out that the OS (i.e., /proc/cpuinfo) disagrees with one of our calculations, we just assume the OS is right. There may not be an MKL-related solution here. Type Rep CPU = D1 (' MetaData "CPU" "System.CPU" "cpuinfo-0.1.0.You can reply as quickly or as slowly as you need. ( Data d, Data e) => c (t d e)) -> Maybe (c CPU) # Data d => c (t d)) -> Maybe (c CPU) #ĭataCast2 :: Typeable t => ( forall d e. r -> c r) -> Constr -> c CPU #ĭataCast1 :: Typeable t => ( forall d. Data b => c (b -> r) -> c r) -> ( forall r. Data d => c (d -> b) -> d -> c b) -> ( forall g. Module is unable to provide information on your system please file a bug With a kernel from the 2.6 branch or later by reading /proc/cpuinfo. In its current state this module can only collect information from Linux systems True of numerical workloads, but as always benchmarking should be employed toĮvaluate the impact of different heuristics. There are in fact two logical cores for each physical core. Some workloads mayīenefit from, for example, using half the number of logical cores available if The Intel Core i7-10850H is a high-end processor for laptops with six cores based on the Comet Lake architecture (CML-H, 4th generation of Skylake). This package allows a program to use information about the physical and logicalįeatures of the available processors as a heuristic for selecting the number of Resources and the thread/spark workloads are similar, then this might be slower This script makes use of the Intel OData API, and requests certain attributes from a given CPU model (e.q. However, if each logical core does not have dedicated physical RTS to simply multiplex Haskell threads or sparks over the number of logicalĬores available. It is common for threaded Haskell programs to be run with +RTS -N, causing the
Resources are doing the same sort of work there will be scheduling contentionįor a single type of execution resource on the physical core.
This is because technologies providing supernumerary logicalĬores typically work by scheduling multiple threads in a shared pool ofĮxecution resources, e.g. Indeed, some parallel workloads may suffer a performance decrease ifĪll logical cores presented by the operating system do not have dedicated These additional logical cores increase the performance of some, but not all Two logical cores for every physical core present on a supported physical Intel's Hyper-Threading is an example of such a technology, capable of providing
Modern hardware provides not only multiple physical processors and physicalĬores, but logical cores which may not have dedicated execution resources. This module provides information about the processors available on a system.