I'm at about the same level - jalapenos are a staple, I use habaneros/scotch bonnets but carefully... (not carefully enough, apparently)
One of my neighbors started growing Naga Jolokias (not sure why, she doesn't like spicy food and her husband won't go near the Nagas) so I have a bunch and am not really sure what to do with them yet. Thinking about mixing up a batch of *really* hot jerk paste (I normally use 6-8 scotch bonnets) but not sure what I'm going to end up with if I grind up a couple of Naga Jolokias instead. One of my friends also picked up a bottle of Blair's 3AM Reserve, which is supposed to be around 3 million scoville units. It's sitting on my kitchen counter and I haven't opened it yet.
Regarding the jump to 600g for new GPU support, the problem is that getting a new GPU running involves a relatively small amount of time writing the initial code and a relatively large amount of time figuring out why the damn thing doesn't work. If you don't start with a 100% known good code base then things get exponentially more complicated. When we started working on Evergreen even 300g wasn't at the point where it felt completely ready to use as the base for new GPU support, but obviously a lot has changed since then. It wasn't a question of knowing the code as much as the framework being ready to "bet the farm" on.
The choice for Evergreen is pretty simple -- we'll probably stay with whatever has the best chance (if any) of getting into the fall distro releases until the code is generally useable (which is probably 600c) then jump to 600g and never look back. Most of the distros are going with somewhat older code so there's probably some backporting required anyways - what we need to look at is whether backporting is feasible or not. If not, then we jump to 600g anyways and make sure everything is shiny for the spring distro releases.
Any new GPU support is going to miss the fall distros anyways so there we have more flexibility and I think going with 600g from day one is going to be the right answer.
One of my neighbors started growing Naga Jolokias (not sure why, she doesn't like spicy food and her husband won't go near the Nagas) so I have a bunch and am not really sure what to do with them yet. Thinking about mixing up a batch of *really* hot jerk paste (I normally use 6-8 scotch bonnets) but not sure what I'm going to end up with if I grind up a couple of Naga Jolokias instead. One of my friends also picked up a bottle of Blair's 3AM Reserve, which is supposed to be around 3 million scoville units. It's sitting on my kitchen counter and I haven't opened it yet.
Regarding the jump to 600g for new GPU support, the problem is that getting a new GPU running involves a relatively small amount of time writing the initial code and a relatively large amount of time figuring out why the damn thing doesn't work. If you don't start with a 100% known good code base then things get exponentially more complicated. When we started working on Evergreen even 300g wasn't at the point where it felt completely ready to use as the base for new GPU support, but obviously a lot has changed since then. It wasn't a question of knowing the code as much as the framework being ready to "bet the farm" on.
The choice for Evergreen is pretty simple -- we'll probably stay with whatever has the best chance (if any) of getting into the fall distro releases until the code is generally useable (which is probably 600c) then jump to 600g and never look back. Most of the distros are going with somewhat older code so there's probably some backporting required anyways - what we need to look at is whether backporting is feasible or not. If not, then we jump to 600g anyways and make sure everything is shiny for the spring distro releases.
Any new GPU support is going to miss the fall distros anyways so there we have more flexibility and I think going with 600g from day one is going to be the right answer.
Comment