downloading 64 bit personal version?

Community Support
1

HI,
I’m trying to download the personal use 64 bit version of kdb.

When I go to download page, https://kx.com/connect-with-us/download/, I only see links for x86 based versions. Do I need to use a different link to download 64 bit version?

thanks for the help!

2

The 64 bit version is free to use, just not for commercial use.

There are some diffs/requirements though, see here - https://kx.com/connect-with-us/download/

Download the 64 bit version from here - https://ondemand.kx.com/

And some quick info kx’s announcement a few months back…

"

64-bit Personal Edition

We are now allowing access to kdb+ on demand to all users for non-commercial use  for free.

The personal edition is not to be used for any commercial purposes, for development of software that will be used commercially, or at licensed customers premises (and you can believe we check that ;) ). 

It is available for 2 machines per developer, and up to 16 cores per machine.

If you need any more information on kdb+ on demand, please email ondemand@kx.com 

"

HTH,

Sean

3

thanks Sean! Couldn’t find that link otherwise. Cool of Kx to do this, and the ‘always on’ requirement seems a good compromise of protecting themselves form abuse

4

Just a quick question: kdb+ on demand PE is restricted to use 16 cores (won’t use more than 16 cores on a machine),
or won’t run on machines with more than 16 cores (eg. dual-socket 2x20 core machines) ?

Thanks,

pahihu

  1. március 14., szerda 11:16:33 UTC+1 id?pontban Sean O’Hagan a következ?t írta:

It is available for 2 machines per developer, and up to 16 cores per machine.

5

When using the on demand license, it’ll exit with 'cores if the number of cores the pid is tasked too, or sees, is more than 16. 

See - http://code.kx.com/q/tutorials/licensing/#core-restrictions

As long as you task/numa correctly, the binary will not abort itself.

You can see the number of cores entitled to a q process by looking at the banner

…w64/ 2(16)core… // note the 2 here is what the process is allowed to use, and the 16 is the licensed amount

or with .z.c - http://code.kx.com/q/ref/dotz/#zc-cores   // note - this doesn’t give physical cores of the system, but rather what the physical number the process is allowed to use

You can also see the licensed number of cores by looking at the first element in your license - ‘first .z.l’, this results in maxCoresAllowed (and 16 is the amount in the case on the on demand license)

http://code.kx.com/wiki/Reference/dotzdotl

Regards,

Sean

6

Thank you for the clarification.
I was not aware of that, because I am on kdb+ 3.3 personal 32bit (prior to September 13, 2015).

pahihu

  1. március 15., csütörtök 12:55:57 UTC+1 id?pontban Sean O’Hagan a következ?t írta:

When using the on demand license, it’ll exit with 'cores if the number of cores the pid is tasked too, or sees, is more than 16. 

See - http://code.kx.com/q/tutorials/licensing/#core-restrictions

As long as you task/numa correctly, the binary will not abort itself.

You can see the number of cores entitled to a q process by looking at the banner

…w64/ 2(16)core… // note the 2 here is what the process is allowed to use, and the 16 is the licensed amount

or with .z.c - http://code.kx.com/q/ref/dotz/#zc-cores   // note - this doesn’t give physical cores of the system, but rather what the physical number the process is allowed to use

You can also see the licensed number of cores by looking at the first element in your license - ‘first .z.l’, this results in maxCoresAllowed (and 16 is the amount in the case on the on demand license)

http://code.kx.com/wiki/Reference/dotzdotl

Regards,

Sean