The only thing I haven't tried is pushing it into the trash bin.
The only thing I haven't tried is pushing it into the trash bin.
delete everything start overhow do you guys generally address capacity issues?
In the case of my current gig... this probably would be a good way to address it.delete everything start over
The level of asshattery that I deal with would make you question your career choice on an hourly basis. Systems are generally specced for a ~5 year cycle with constant growth during that time so there generally aren't too many capacity surprises for my industry.I'm constantly telling the mgmt/directorships that we're out of capacity. Storage, compute, you name it - if it's capacity, we're out of it.
@6thElement - how do you guys generally address capacity issues?
So are they purchased with the capacity at the outset? i.e. you buy storage infrastructure with current+5y growth in mind? Or do you just plan on purchasing *as* you grow to address capacity? Capacity-on-demand type decisions?The level of asshattery that I deal with would make you question your career choice on an hourly basis. Systems are generally specced for a ~5 year cycle with constant growth during that time so there generally aren't too many capacity surprises for my industry.
That sounds exactly how they plan and build roads around here.So are they purchased with the capacity at the outset? i.e. you buy storage infrastructure with current+5y growth in mind? Or do you just plan on purchasing *as* you grow to address capacity? Capacity-on-demand type decisions?
Here it *appears* that they buy with 5y lifespan in mind, but ONLY for current capacity without any budget/plan whatsoever for growth. Despite the fact that everyone KNOWS that growth is going to happen...
![]()
Focking windy out there.
Fucking work...![]()
It's not just computers from my vantage point.
![]()
I have to work overtime just so I can be here long enough to hate everyone, and that’s not even allowing enough time for proper hatred.It's not just computers from my vantage point.
![]()
Procured with the capacity to meet the needs of the 5 years. Probably very static compared to what you work with system wise.So are they purchased with the capacity at the outset? i.e. you buy storage infrastructure with current+5y growth in mind? Or do you just plan on purchasing *as* you grow to address capacity? Capacity-on-demand type decisions?
Here it *appears* that they buy with 5y lifespan in mind, but ONLY for current capacity without any budget/plan whatsoever for growth. Despite the fact that everyone KNOWS that growth is going to happen...
![]()
The thing that drives me crazy is that growth is pretty easy to demonstrate... you know, with *data* - and yet, decisions continue to be made that appear to completely ignore the data.Procured with the capacity to meet the needs of the 5 years. Probably very static compared to what you work with system wise.
Sounds like someone downstream is paid not for increasing revenues but by eliminating costs?The thing that drives me crazy is that growth is pretty easy to demonstrate... you know, with *data* - and yet, decisions continue to be made that appear to completely ignore the data.
It's like a simple graph like this is indecipherable to those with the hands on the money-sack:
View attachment 128190
Of course it's indecipherable, there are no label or units for the Y-axis.The thing that drives me crazy is that growth is pretty easy to demonstrate... you know, with *data* - and yet, decisions continue to be made that appear to completely ignore the data.
It's like a simple graph like this is indecipherable to those with the hands on the money-sack:
View attachment 128190
"just delete some of the old pr0n"The thing that drives me crazy is that growth is pretty easy to demonstrate... you know, with *data* - and yet, decisions continue to be made that appear to completely ignore the data.
It's like a simple graph like this is indecipherable to those with the hands on the money-sack:
View attachment 128190
parsecs.Of course it's indecipherable, there are no label or units for the Y-axis.
Nice bikes.got wore the eff out on a 27 mile ride in the mountains. not even all that much climbing but dang, i’m apparently not in the best of shape. pic at the start of raiders (for nc monkeys who know) where the “no bikes” sticker has “mysteriously” been replaced by a bikes allowed sticker. 60* and sunny. other than lots of downfall that needs to be cleared, excellent conditions. beers afterwards, of course.![]()
Blame the users.I'm constantly telling the mgmt/directorships that we're out of capacity. Storage, compute, you name it - if it's capacity, we're out of it.
@6thElement - how do you guys generally address capacity issues?
Ee to the kay tee dollars?The thing that drives me crazy is that growth is pretty easy to demonstrate... you know, with *data* - and yet, decisions continue to be made that appear to completely ignore the data.
It's like a simple graph like this is indecipherable to those with the hands on the money-sack:
View attachment 128190
dude on the giant tore it the eff up on some rugged trails on that xc rig. he’s also like half my age, which may explain why i am le tired.Nice bikes.![]()
Is that an Anthem?dude on the giant tore it the eff up on some rugged trails on that xc rig.
This is why you're fatdude on the giant tore it the eff up on some rugged trails on that xc rig. he’s also like half my age, which may explain why i am le tired.
in other news, it appears that i have somehow eaten an entire quart of guacamole
I question that.This is why you're fat