What Are You Doing Right Now
-
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
Like what? I did a Get-Uptime cmd and it was instant. If it was any faster, I wouldn't notice.
It's not instant. Are you sure you didn't spend time getting PS up and running first, THEN time only the command after all the time was already spent?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
-
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
Like what? I did a Get-Uptime cmd and it was instant. If it was any faster, I wouldn't notice.
It's not instant. Are you sure you didn't spend time getting PS up and running first, THEN time only the command after all the time was already spent?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
Weird,
-
@dbeato said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
Like what? I did a Get-Uptime cmd and it was instant. If it was any faster, I wouldn't notice.
It's not instant. Are you sure you didn't spend time getting PS up and running first, THEN time only the command after all the time was already spent?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
Weird,
@Obsolesce said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
No, nothing new or fancy... just plain old PS6:
-
@scottalanmiller said in What Are You Doing Right Now:
Speed of uptime on Linux. This is bash calling SSH calling bash...
One second. Most of that time is used to set up SSH, nothing to do with Bash.
I can do that exact same thing in PowerShell on Win10 now that SSH works by default
word for word... letter for letter.... in PowerShell.
-
@Obsolesce said in What Are You Doing Right Now:
I can do that exact same thing in PowerShell on Win10 now that SSH works by default
word for word... letter for letter.... in PowerShell.I've been ABLE to do it for a while. It's the speed that isn't there. We use PowerShell over SSH every day (until a few weeks ago when PS totally broke and our long standing processes all failed because Windows didn't keep PS consistent.) But it is still crazy slow compared to any other platform. Certainly an improvement, joining us with late 1990s technology. But it doesn't address the speed issue.
-
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
I can do that exact same thing in PowerShell on Win10 now that SSH works by default
word for word... letter for letter.... in PowerShell.I've been ABLE to do it for a while. It's the speed that isn't there. We use PowerShell over SSH every day (until a few weeks ago when PS totally broke and our long standing processes all failed because Windows didn't keep PS consistent.) But it is still crazy slow compared to any other platform. Certainly an improvement, joining us with late 1990s technology. But it doesn't address the speed issue.
-
It did it above instantly (minus asking for password, just a test machine don't have that set up)
I noticed zero speed difference than when I do it on Linux with BASH.
-
@Obsolesce said in What Are You Doing Right Now:
@dbeato said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
Like what? I did a Get-Uptime cmd and it was instant. If it was any faster, I wouldn't notice.
It's not instant. Are you sure you didn't spend time getting PS up and running first, THEN time only the command after all the time was already spent?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
Weird,
@Obsolesce said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
No, nothing new or fancy... just plain old PS6:
Yeah, I have only 5.1
-
@dbeato said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@dbeato said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
Like what? I did a Get-Uptime cmd and it was instant. If it was any faster, I wouldn't notice.
It's not instant. Are you sure you didn't spend time getting PS up and running first, THEN time only the command after all the time was already spent?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
Weird,
@Obsolesce said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
No, nothing new or fancy... just plain old PS6:
Yeah, I have only 5.1
that's because PSC6 is not a part of any OS natively. It is a new "add on", optional side by side installation that you can add to Windows or Linux.
So yes, it is available. but it is not standard or built in, so things like Get-Uptime are not yet part of Windows.
-
@Obsolesce said in What Are You Doing Right Now:
It did it above instantly (minus asking for password, just a test machine don't have that set up)
I noticed zero speed difference than when I do it on Linux with BASH.
That's because you specifically skipped the whole problem. You didn't time PS setting up, you set it up, then timed bash. Of course it came back fast, it was bash not PS that you timed!
-
@scottalanmiller said in What Are You Doing Right Now:
@dbeato said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@dbeato said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
Like what? I did a Get-Uptime cmd and it was instant. If it was any faster, I wouldn't notice.
It's not instant. Are you sure you didn't spend time getting PS up and running first, THEN time only the command after all the time was already spent?
No, I did the exact same thing I'd have done on a Linux GUI....
- Click on PowerShell on the task bar to open it up. (keybind would work too)
- Typed in
Get-Uptime -Since, hit enter. - Maybe I saved a little time typing with PowerShell because of tab-completion. I only typed
get-up <tab> -<tab>thenenter.
Weird,
@Obsolesce said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@black3dynamite yeah, PowerShell is still stuck in like 1982 here.
No, I think all of you are stuck in 1982 while PowerShell has moved on...
Unless there's a bleeding-edge version of Powershell out now that has that cmdlet, it doesn't seem to be native for 5.1.
I know there's a module out there that does what your picture shows, but it would be nice if that was just baked-in.
No, nothing new or fancy... just plain old PS6:
Yeah, I have only 5.1
that's because PSC6 is not a part of any OS natively. It is a new "add on", optional side by side installation that you can add to Windows or Linux.
So yes, it is available. but it is not standard or built in, so things like Get-Uptime are not yet part of Windows.
But what we are currently talking about, SSH, works on 5.1 anyways.
Earlier was one specific well-known case.
-
@Obsolesce said in What Are You Doing Right Now:
But what we are currently talking about, SSH, works on 5.1 anyways.
The discussion is about how slow PS is. All mentioning of SSH was that Bash was SO much faster than PS, that I'm able to SSH to remote boxes and run a bash command and tear down the SSH tunnel all faster than PS can launch.
-
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
It did it above instantly (minus asking for password, just a test machine don't have that set up)
I noticed zero speed difference than when I do it on Linux with BASH.
That's because you specifically skipped the whole problem. You didn't time PS setting up, you set it up, then timed bash. Of course it came back fast, it was bash not PS that you timed!
I didn't set up PowerShell... what do you mean by set it up?
PowerShell opens the same speed as terminal opens before I start typing. Am I missing something or some context from somewhere?
-
@Obsolesce said in What Are You Doing Right Now:
I didn't set up PowerShell... what do you mean by set it up?
You sure did, it's there on the screen. Can't be if you didn't set it up. PowerShell's slowness almost entirely comes from its load time.
-
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
But what we are currently talking about, SSH, works on 5.1 anyways.
The discussion is about how slow PS is. All mentioning of SSH was that Bash was SO much faster than PS, that I'm able to SSH to remote boxes and run a bash command and tear down the SSH tunnel all faster than PS can launch.
I asked for a real example, you gave SSH.
-
@Obsolesce said in What Are You Doing Right Now:
I asked for a real example, you gave SSH
No, I gave Uptime
-
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
I asked for a real example, you gave SSH
No, I gave Uptime
Via SSH. Which is the same when done through PowerShell.
-
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
I asked for a real example, you gave SSH
No, I gave Uptime
Via SSH. Which is the same when done through PowerShell.
No, not through SSH. You missed the entire point to the point that you tested bash twice and never PowerShell. You've missed all of it. We aren't on the same subject. I'm discussing absolutely nothing but how slow PS is, nothing else. Not SSH speed, not at all.
-
Simple example... no Linux, just PS vs CMD. Same command...
[scott@lax-lnx-jump ~]$ time ssh strongbad@strongbad "@powershell ls"
....real 0m1.772s
user 0m0.044s
sys 0m0.015s
[scott@lax-lnx-jump ~]$ time ssh strongbad@strongbad dir
.....real 0m0.845s
user 0m0.043s
sys 0m0.011sSame command, same box, PowerShell took twice as long as CMD.
-
I'm using SSH only to give me a simple way to time the transaction. Because I have no idea how to get this time from inside Windows.
