vrv

7 ms·

1.
by vrv 5mo ago
MintMCP | Founding Engineer / Founding GTM | SF Bay Area (ONSITE) MintMCP helps enterprises safely roll out agents to the entire organization (e.g, governance around MCP tools and agents like Claude Code / Codex / Cowork). We
2.
by vrv 6mo ago
MintMCP | Founding Engineer / Founding GTM | SF Bay Area (ONSITE) MintMCP helps enterprises safely do more with Agents (e.g, governance around MCP tools and agents like Claude Code / Cowork, and others). We're building an MC
3.
by vrv 1y ago
Agreed, OAuth is certainly preferred for many reasons, but replace "API keys" with "OAuth access tokens" and you have the same fundamental challenge of ensuring an LLM or untrusted code never has access to the user'
4.
by vrv 1y ago
If the output schema specifies an id field, the LLM can write a code snippet that references it based on the context of the subsequent request, but the LLM doesn't need to observe the underlying value unless necessary. E.g., it can pas
5.
by vrv 8y ago
bfloat16 was first in DistBelief, so it actually predates TensorFlow and TPUs (I worked on both systems). IIRC the motivation was more about minimizing parameter exchange bandwidth for large-scale CPU clusters rather than minimizing memory
6.
by vrv 9y ago
Thanks for mentioning that Sam, I appreciate it. Speaking for just myself: I personally don't care what tools or frameworks people use to get work done and have repeatedly suggested people use whatever works best for them. It also wou
7.
by vrv 9y ago
I'm sorry to hear of that experience, and it's certainly not intentional. We should (and I will) always try to be better (I know some will forever view Google as an antagonistic behemoth but usually the engineers on both sides ar
8.
by vrv 9y ago
The codebase in GitHub is pretty much exactly the same as the internal, the main exceptions being things like having to rewrite include paths for files, filesystem plugins for internal cluster filesystems, etc; and those things are modulari
9.
by vrv 10y ago
(I made this change anyway).
10.
by vrv 10y ago
wrt GPU memory: If we made InteractiveSession by default grow memory, would that work for you? Seems sensible to change the default for InteractiveSession (e.g., for use in notebooks), but not the default for Session (production training &
11.
by vrv 10y ago
TensorFlow doesn't yet do loop fusion (though I believe the specific example shown in that article may already be done via constant folding). But if you have a bunch of elementwise operations, JIT-techniques can reduce the number of m
12.
by vrv 10y ago
Windows support is definitely being worked on and lots of progress has been made, so it will eventually arrive -- just lots of little details to work out, but we're optimistic it'll come soon.
13.
by vrv 10y ago
For what it's worth, we're hoping to integrate these APIs into our iOS version of the TensorFlow runtime, so you can maintain graph portability but still get the benefits of the optimized implementation on the platform. We only ju
14.
by vrv 10y ago
FYI, TF now supports: 1) dynamic RNNs, 2) bidirectional RNNs and will soon have 3D convolution -- that comparison is a little out of date.
15.
by vrv 10y ago
The arxiv paper is just a repost of the preliminary paper, which is really more a design outline and rationale -- we may work on a more substantial paper later, we've been busy building the software.
16.
by vrv 10y ago
I believe our published wheels now include the code for cuda compute 3.0, so it should work out of the box now. (as long as the images have cudnn v4 and cuda 7.5 installed, I think :)
17.
by vrv 10y ago
It's on the roadmap: https://www.tensorflow.org/versions/r0.8/resources/roadmap.h...
18.
by vrv 10y ago
(Do you have an example link that doesn't work? I clicked a bunch of links there and they were all working. Feel free to file a bug at github.com/tensorflow/tensorflow)
19.
by vrv 10y ago
And even those numbers on the front page are out of date :) (we're even faster now: https://github.com/soumith/convnet-benchmarks/pull/96 , which is from a few weeks ago.) The field is moving quickly eno
20.
by vrv 10y ago
In our issues template, we start it with: "GitHub issues are for bugs / installation problems / feature requests. For general support from the community, see [StackOverflow](link)" However, we still get plenty of issue
21.
by vrv 11y ago
Can you point me to "current memory utilization" numbers you're referring to?
22.
by vrv 11y ago
Indeed we are. Here's a recent commit from today https://github.com/tensorflow/tensorflow/commit/d6f3ebfdfc1d... :)
23.
by vrv 11y ago
Keeping that up-to-date and useful is as hard as keeping benchmarks in Deep Learning up to date ;)
24.
by vrv 11y ago
Yeah, those are just cards we know that work: we don't have all possible GPUs to test our 20+ changes a day on, so we can't formally guarantee it will work on older cards, but in general we try our best to keep it all working for
25.
by vrv 11y ago
Feel free to ping us (TensorFlow) on github issues to get installation issues resolved -- on cudnn r4 we're doing much better, and we're soon to check in a series of changes to get us roughly on par with Torch on cudnn r4. We&#x27
26.
by vrv 11y ago
One suggestion is to improve the permissions system. For example, third-party github plugins that interact with the github system (e.g., setting labels, responding to comments) require "write permissions" which gives those system
27.
by vrv 11y ago
Okay, after a bunch of last minute python 3 issues, we've updated the documentation and packages, so everything should be ready.
28.
by vrv 11y ago
The original public release was great to identify many potential installation issues that we couldn't possibly test ahead of time -- hopefully this next upcoming release will address some of your issues. Otherwise, please file an issue
29.
by vrv 11y ago
There will eventually be more up to date numbers -- we can only ask so much of Soumith's time. In addition, getting on par with cudnnv2 is just the first step. cudnnv3/v4 and cuda7.5 are next up.
30.
by vrv 11y ago
I've read some people have been able to do hacks to get it to work, but I agree we need to make it easier. The full configurability for other cudnn versions didn't make 0.6.0 but might be in a patch update sometime soon. It&#x27

More ›