Anyway to control how many CPUs Runtime.availableProcessors() sees in a zone?

Only with pools I think.

illumos.org/man/8/psrset ?

In general it's hard to lie about the number of CPUs unless you're not going to be scheduled across them.

gist.github.com/dekobon/305883fb6d776b0c9fc1 What looking at this to help a user out maybe

I think that's the underlying bit, but it needs to go through other stuff.

I'm not 100% sure that this user is hitting this problem, his code at first glance looked a bit suspect

This is a problem container problem.

Smithx10: you can also write an interposer to return a specific value to the JRE IIRC -- though you'd need to see if the code you're running cares about what CPU a thread is running on or not

which makes it hard for it to be a general solution

if it doesn't and just is using it to (for example) control the # of threads created or for other sizing

it's probably fine

but if it does, it may get upset if say you tell them there's 8 CPUs and it sees something running on cpu15

We did some work in SmartOS to limit the number of visible CPUs in a zone, but apps start breaking in bad ways when they find out their thread is running on cpu 9 and we told them there are only 4 cpus.

Because of that, we ultimately had to abandon that work.

heh

sommerfeld: Thanks for that. I'll look at those after I get the same treatment done to topo_mod_dprintf which is ... heinous.

rmustacc - Oh, it is.. I have done a few fixes after being confused by debug messages printing `0` instead of the real value of the topo_instance_t, but thanks for doing a complete overhaul there. I imagine it's quite a lot of PRId64!

[illumos-gate] 14639 Add pkg-config support for libuuid - provide uuid.pc files -- Klaus Ziegler <klausz⊙hd>

BTW, the cat's out of the bag: illumos.topicbox.com/groups/develop…a53edeb5c-M821cc18b5884e04e16daa8fd

andyf: PRIu64 and a few more egregious things, but I'll have something up shortly.

anyone have any pointers/links that'd help decode the various values from an ereport.io.pci.fabric event?

They're all the PCIe AER cap fields for the most part.

So if you don't have the spec, pcieadm explains them a bit. I can try to get a better bit.

Also if you gist it I can try to explain it, which may be better than nothing.

that's an example one

there's several.. i haven't had a chance to see if they're all identical

(there was 7 of them all in less than 1s)

User ended up using 'JAVA_OPTS="-XX:ActiveProcessorCount=2 -XX:-UseGCTaskAffinity -XX:-BindGCTaskThreadsToCPUs -XX:ParallelGCThreads=4 -Djava.util.concurrent.ForkJoinPool.common.parallelism=4"' and his application behaved much better, what was saturating the CPU_CAP in the zone now is hanging at 70 / 200

btw, weren't you having the issue of slow VM startup because of i40e + jumbo frames?

greeting ommited as nohello.com, and re-inserted to wish everyone a wonderful day :D My experience with *nix operating systems is mostly bound to linux, and I would love to run illumos on my server. It's perfectly supported from what I can see, but before I start, I would like to know what key differences I may find as I adjust to a new system.

as per*

are there any resources I should know of?

one difference is that illumos isn't just a kernel, it's a kernel+core userland bits, distros take that core bit to produce something that you run.. the most common illumos distros generally have a fair amount of documentatino

and the man pages for the common illumos stuff are often pretty good

if you've identified a specific distro you want to mess with, that might be a good start

someone might be able to give you more specific pointers

well, you see the thing is I have never opened the man pages in my life... not to say I don't know anything, but I learned through trial and error with a mountain of useless questions. Now I am not looking to do that again, because I have learned to value my own time and the time of others, so I guess it would be more accurate to ask "where shoudl I look to find an answer on my own and how should I go about looking?" "

as for a distro, I was considering openindiana

My first experience with illumos was wrestling with missing drivers on an unsupported device, and my attempts to problem solve the issue lead me down a rabbit hole which convinced me that eMMC devices were not even supported in the kernel. It was more of an experiment than anything, but it shows my natural approach is subpar.

oh yeah I guess I was also curious on if it's better to mount 6 hdds as a hardware raid or make a ZFS pool using individual disks.

In general we recommend using ZFS for that kind of operation.

That way you're not subject to the controller's battery or have the hardware raid hole which comes up with RAID 5/6.