Jonkman Microblog
  • Login
Show Navigation
  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices by thurloat πŸ“Œ (thurloat@mastodon.club), page 48

  1. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Wednesday, 12-Dec-2018 09:49:38 EST thurloat 📌 thurloat πŸ“Œ

    i t i s w e d n e s d a y m y d u d e s

    In conversation Wednesday, 12-Dec-2018 09:49:38 EST from mastodon.club permalink
  2. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Wednesday, 12-Dec-2018 07:32:58 EST thurloat 📌 thurloat πŸ“Œ
    in reply to
    • Oneesan succubus

    @lain is it behind a flag, or is no one using it? i'm on 65, and still see my beautiful scrollbars everywhere.

    In conversation Wednesday, 12-Dec-2018 07:32:58 EST from mastodon.club permalink
  3. keithzg (keithzg@mastodon.club)'s status on Tuesday, 11-Dec-2018 20:24:57 EST keithzg keithzg

    "Please keep your e’s to a minimum, folks, there are people trying to perform capitalism here." https://linuxwit.ch/blog/2018/12/everything-that-lives-is-designed-to-end/

    In conversation Tuesday, 11-Dec-2018 20:24:57 EST from mastodon.club permalink Repeated by thurloat
  4. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 19:43:04 EST thurloat 📌 thurloat πŸ“Œ
    • alex

    @catalina uh oh, whats happenin

    In conversation Tuesday, 11-Dec-2018 19:43:04 EST from mastodon.club permalink
  5. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 18:17:55 EST thurloat 📌 thurloat πŸ“Œ
    • Manu de :montreal:, :aquebec:

    @manu heh, just my 2 year old :)

    In conversation Tuesday, 11-Dec-2018 18:17:55 EST from mastodon.club permalink
  6. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 18:15:15 EST thurloat 📌 thurloat πŸ“Œ

    thank you for your time.

    love Ezra.

    In conversation Tuesday, 11-Dec-2018 18:15:15 EST from mastodon.club permalink
  7. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 18:14:47 EST thurloat 📌 thurloat πŸ“Œ
    in reply to

    , llollllllllllllllllllllllllll.lllllllllllllllllllkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk kkkkkkkkkkkkkkkkkkkkkkm kk kk llllllllllllllllk

    In conversation Tuesday, 11-Dec-2018 18:14:47 EST from mastodon.club permalink
  8. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 18:13:54 EST thurloat 📌 thurloat πŸ“Œ
    in reply to

    bv i888

    In conversation Tuesday, 11-Dec-2018 18:13:54 EST from mastodon.club permalink
  9. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 18:13:40 EST thurloat 📌 thurloat πŸ“Œ
    in reply to

    t g g v n mumuk8k8k

    In conversation Tuesday, 11-Dec-2018 18:13:40 EST from mastodon.club permalink
  10. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 18:13:14 EST thurloat 📌 thurloat πŸ“Œ
    in reply to

    bny df b vf nhj b

    In conversation Tuesday, 11-Dec-2018 18:13:14 EST from mastodon.club permalink
  11. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 18:12:55 EST thurloat 📌 thurloat πŸ“Œ

    m h gnthn j mimi}
    .;kmk nm,k.l i0pklo0;k/kl';[pnmhju, l,,lkjuuty5t666yt

    In conversation Tuesday, 11-Dec-2018 18:12:55 EST from mastodon.club permalink
  12. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 10:34:41 EST thurloat 📌 thurloat πŸ“Œ
    in reply to
    • M. GrΓ©goire

    @mpjgregoire yea the procurement system is set up pretty strangely.

    my sources close to the mil procurement process say it's equally as frustrating and drawn out as the public sees it, they wish they could pull the trigger on stuff without all the bureaucracy.

    In conversation Tuesday, 11-Dec-2018 10:34:41 EST from mastodon.club permalink
  13. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 10:13:17 EST thurloat 📌 thurloat πŸ“Œ
    • yukiameπŸ–•Quantum_Yuki

    @yukiame of course! not arguing virtualization is bad.

    The difference between 100 customers experiencing degraded performance, and 20 is important. When you extrapolate it, say 5% of your 10,000 customers run intensive VMs. If the design is such that your 5% of customers negatively impact 10% an additional of customers, vs. 2-5% -- that is substantial.

    And can't huddle all the "bad" VMs on a few nodes, because they're likely high paying and you'd have an exodus.

    In conversation Tuesday, 11-Dec-2018 10:13:17 EST from mastodon.club permalink
  14. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 10:00:20 EST thurloat 📌 thurloat πŸ“Œ
    • :debian: πšœπšŽπš•πšŽπšŠ :opensuse:

    @selea yea I know some folks that run Nutanix stuff. They've generally had pretty good experiences.

    Mostly because of the way we run our business, hyperconverged has never really been an option once we grew up.

    In 2013ish we actually had a HCI-ish design for compute and storage, we aptly named that time period in the company a "GlusterFuck".

    In conversation Tuesday, 11-Dec-2018 10:00:20 EST from mastodon.club permalink
  15. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 09:54:28 EST thurloat 📌 thurloat πŸ“Œ
    • yukiameπŸ–•Quantum_Yuki

    @yukiame intelligent hypervisors aren't going to make business decisions for you.

    designing compute infrastructure to have a 100VM blast radius for a single node is going to force you into facing the trolley problem at a larger scale. Minimizing the blast radius of any failure is critical, and smashing performance / capacity limits are a design failure.

    In conversation Tuesday, 11-Dec-2018 09:54:28 EST from mastodon.club permalink
  16. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 09:44:08 EST thurloat 📌 thurloat πŸ“Œ
    • :debian: πšœπšŽπš•πšŽπšŠ :opensuse:

    @selea hopefully at that point they have some SAN cluster or NVMe fabric storage.

    In conversation Tuesday, 11-Dec-2018 09:44:08 EST from mastodon.club permalink
  17. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 09:38:28 EST thurloat 📌 thurloat πŸ“Œ
    • It's a me

    @feld they've got thermal density to take care of with increased power limit as well, if you're getting more then they're borrowing from someone else if its not already packed like sardine tins in there.

    obviously depends how seriously the facility takes the limits of their design.

    In conversation Tuesday, 11-Dec-2018 09:38:28 EST from mastodon.club permalink
  18. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 09:34:35 EST thurloat 📌 thurloat πŸ“Œ
    in reply to
    • nia, cat wife πŸ’œ

    @scarlett anti-socks software users

    In conversation Tuesday, 11-Dec-2018 09:34:35 EST from mastodon.club permalink
  19. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 09:34:02 EST thurloat 📌 thurloat πŸ“Œ
    • nia, cat wife πŸ’œ

    @scarlett is this a thing?

    or did i get memed?

    In conversation Tuesday, 11-Dec-2018 09:34:02 EST from mastodon.club permalink
  20. thurloat πŸ“Œ (thurloat@mastodon.club)'s status on Tuesday, 11-Dec-2018 09:31:45 EST thurloat 📌 thurloat πŸ“Œ

    people who put 3TB of ram and dual 32 core procs in a 1U virtualization server expecting to host 100 VMs, but don't realize there is such a thing as memory bandwidth.

    one or two intensive VMs, and everyone is having a bad time.

    then your 40U colo rack in the DC can only have 10U populated because you've hit your power limit.

    In conversation Tuesday, 11-Dec-2018 09:31:45 EST from mastodon.club permalink
  • After
  • Before
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.