You can add Splunk to the list of companies with a similar clause. As a Splunk competitor it makes sales a bit harder initially (we can show our product's numbers, but nothing to compare them against), but if you can convince customers to set up a head-to-head proof-of-concept of their own , well, they tend to figure out why Splunk doesn't want you publishing benchmarks...
DeWitt Clause, or can you benchmark %database% and get away with it
51–60 of 93 posts
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#52You can add Splunk to the list of companies with a similar clause. As a Splunk competitor it makes sales a bit harder initially (we can show our product's numbers, but nothing to compare them against), but if you can convince customers to set up a head-to-head proof-of-concept of their own , well, they tend to figure out why Splunk doesn't want you publishing benchmarks...
I love Splunk, it works so well after data is ingested so... who are you if you're better?
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#53It would be quite refreshing if we could have a story in which Oracle are the good guys for once. I'm sure they are at least purchasing some modern-day 'indulgences' by - for instance - donating food to starving north korean elites?
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#54Earlier quoted context omitted.
If Oracle ever wants to be the good guys just once, I have an idea for them that's right in their wheelhouse. Step 1: buy grsecurity's kernel hardening patches. Step 2: put said patches in the publicly released UEK source. Step 3: wait for grsecurity to refuse to give them future patches. Step 4: sue grsecurity for imposing further restrictions on the exercise of rights granted by the GPL.
I think the weakness of your model is just because you have the right to distribute a certain patch level that does not mean you automatically have the right to distribute further patches, Conversely, If the right to distribute is revoked, say a GPL to closed source license change you have still the right to distribute any versions originally distributed under the open license. A good example off all this is the sord…
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#55Earlier quoted context omitted.
They try to be the good guy. Their free tier is quite extensive (24GB of RAM, 4 ARM vCPUs and ±2 AMD cores, a several hundred GB of storage), good enough to run quite a decent personal cluster on, probably to lure in businesses for their AWS-style cloud services which are as ridiculously expensive as their competition. However, just like AWS, Azure, and GCloud, their admin UI is complicated, slow, frustrating and ful…
I've read various stories over the years about Oracle extremely aggressively pushing high bills because they think you're using the "free" version of MySQL or VirtualBox in a way that you're supposed to pay for it. I'd be very wary running anything "free" from Oracle (as in: I wouldn't).
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#56You can add Splunk to the list of companies with a similar clause. As a Splunk competitor it makes sales a bit harder initially (we can show our product's numbers, but nothing to compare them against), but if you can convince customers to set up a head-to-head proof-of-concept of their own , well, they tend to figure out why Splunk doesn't want you publishing benchmarks...
Can you give your name ? I'm fighting against our Splunk decommission project because the big boys tell us we can just use ELK, to which we reply that it means months of devs to reproduce Splunk abilities, to which they reply human cost is invisible but license cost is a sore point for the board... I love Splunk, it works so well after data is ingested so... who are you if you're better?
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#57You can add Splunk to the list of companies with a similar clause. As a Splunk competitor it makes sales a bit harder initially (we can show our product's numbers, but nothing to compare them against), but if you can convince customers to set up a head-to-head proof-of-concept of their own , well, they tend to figure out why Splunk doesn't want you publishing benchmarks...
Can one provide a benchmarking suite that anyone can execute without posting the results of the test? Thus allowing others to run the test themselves easily but not putting you on the hook for the result?
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#58It would be quite refreshing if we could have a story in which Oracle are the good guys for once. I'm sure they are at least purchasing some modern-day 'indulgences' by - for instance - donating food to starving north korean elites?
If Oracle ever wants to be the good guys just once, I have an idea for them that's right in their wheelhouse. Step 1: buy grsecurity's kernel hardening patches. Step 2: put said patches in the publicly released UEK source. Step 3: wait for grsecurity to refuse to give them future patches. Step 4: sue grsecurity for imposing further restrictions on the exercise of rights granted by the GPL.
Another good thing Oracle could do, is to release a CDDL update that is GPL-compatible.
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#59If you want to benchmark for internal reasons you don't publish the results and nobody knows. If you want to make a service to the community, run your benchmarks, download Tor and publish the results anonymously. I don't see what the big deal is? Is this only limited to marketing claims where you post it on your company's website?
How likely is it that one takes an anonymous benchmark published by a noname researcher seriously?
This isn't line the traditional case of no name vs trusted name: due to the law you _must_ br anonymous to post this, so anonymity isn't a red flag, it's the standard.
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#60Honestly, the presence of that clause screams to me "this app sucks and we'll sue you if you tell anyone how badly". That may not be the case whatsoever, but my first assumption is that they're trying to hide terrible performance.
While I would prefer if this clause was not a thing, I also understand why it exists even for great products. It is surprisingly difficult to reproduce many workload benchmarks and quite easy to engineer a benchmark that misrepresents real-world database performance. There are tools that exist to generate optimally pathological workloads that target specific database implementations, while looking completely reasonab…
We should all be free to express our thoughts and backing data, and participate freely in the marketplace of ideas.
No corporation should be able to put gag orders on people especially when they are biased and have good reasons to want to control the discourse