popoto.backends.postgres.longtail¶
popoto.backends.postgres.longtail
¶
The long-tail memory fields on Postgres (#759 M5; plan §2 H, §3).
Three Redis features that each owned a Lua script, stored natively:
======================= =====================================================
feature Postgres
======================= =====================================================
CyclicDecayField the decay clock is the field's own double
precision column, as for DecayingSortedField
(M2a); the learned cycles are four parallel
double precision[] columns, <f>__cycle_period,
<f>__cycle_amp, <f>__cycle_phase and
<f>__cycle_base (the #698 declared baseline,
NULL element = unknown), and the homeostatic
pressure two double precision columns,
<f>__pressure_rate and <f>__pressure_at
(last_resolved). NULL = no companion-hash
entry. CYCLIC_DECAY_LUA is a SQL expression
(:func:cyclic_score_sql) that rank_decayed,
composite_score's decay arm and the assembler's
score proxy rank with; CYCLES_MERGE_LUA is part of
the save's upsert (:func:cyclic_save_parts);
CYCLES_ADJUST_LUA is one UPDATE
(strengthen_cycle / weaken_cycle).
TDValueField a numeric column, as DecimalField;
TD_UPDATE_LUA is one UPDATE that writes the
new value through the script's %.14g.
PredictionLedgerMixin two engine tables, popoto_prediction_ledger
(model, member, entry jsonb, lua_packed) -- the
$PL:{Class}:meta:{pk} hash entry -- and
popoto_prediction_error (model, part, member,
error) -- the $PL:{Class}:errors:{part} sorted
set. RESOLVE_PREDICTION_LUA is one statement.
======================= =====================================================
Why arrays and not jsonb (plan §3 said jsonb): the cycle amplitudes
are doubles the score multiplies, and jsonb numbers are numeric,
which cannot hold NaN or ±Infinity (an amplitude can be either: a
declared float("inf") passes the field's validation) and would add a text
round trip to every row a ranking scans. A float8[] keeps every bit.
Bit-exactness¶
Every number the scripts compute is computed here operation for operation in
double precision, in the script's order of evaluation: cos and
power are the platform's libm on both servers, as for M2a's decay
expression. Where C saturates (inf / 0) and Postgres would raise
(value out of range, input is out of range for cos(inf)), the
clamped helpers of :mod:.memory take over; the plain expression is used
for every row whose inputs lie in a box where no step can leave the double
range. Numbers the scripts return went through Lua's tostring
(%.14g), and numbers they store through cmsgpack, which packs an
integral number as an integer: :func:lua_num and :func:lua_repack apply
the same rules on the way out.
CyclicSave
dataclass
¶
What one save does to its cyclic fields' state (the
CYCLES_MERGE_LUA run on_save makes on Redis).
Source code in src/popoto/backends/postgres/longtail.py
report(obj, old)
¶
Emit on_save's #698 reset log line for each declared amplitude
that won the merge, from the row's previous cycles (RETURNING
old.…).
Source code in src/popoto/backends/postgres/longtail.py
LongtailOpsMixin
¶
The field_call adapters of this module, for
:class:~popoto.backends.postgres.PostgresBackend.
Source code in src/popoto/backends/postgres/longtail.py
782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 | |
lua_tonumber(value)
¶
Lua 5.1 tonumber of an ARGV string (str(value)), else
nil (None): C strtod -- leading space, a sign, a decimal or
C99 hex float ("0x10" is 16, "0x1p3" 8), inf/infinity/
nan (or nan(chars)) in any case, overflow to ±inf and
underflow to ±0 -- with only trailing space after it, and nothing
read past a NUL (Lua reads the C string). Checked case by case against Redis 8.10's
tonumber (tests/test_backend_parity_longtail.py). Python's
float() is looser (digit separators, non-ASCII digits) and refuses
hex, so the shape is matched first.
Source code in src/popoto/backends/postgres/longtail.py
lua_num(value)
¶
A Lua number as cmsgpack packs it and msgpack reads it back: an
integer when it is integral and fits int64 (-0.0 -> 0), else
the float (a float32 encoding, when exact, decodes to the same
double).
Source code in src/popoto/backends/postgres/longtail.py
lua_repack(value)
¶
value after cmsgpack.unpack then cmsgpack.pack -- what a
script that read-modify-writes a msgpack entry stores. Raises
ValueError where the unpack itself would fail.
Source code in src/popoto/backends/postgres/longtail.py
declared_cycles(cycles)
¶
A field's cycles as the script receives them: each slot
str()-ed into ARGV and tonumber-ed back (phase or 0).
Source code in src/popoto/backends/postgres/longtail.py
merge_cycles(stored, declared)
¶
CYCLES_MERGE_LUA's cycles half: (output, resets).
stored is [(period, amplitude, baseline)] (None = no entry).
Declared cycles are matched to stored ones by period, FIFO within a
period; a picked entry keeps its learned amplitude unless its recorded
baseline differs from the declared amplitude (the developer edited the
declaration: a reset). Output entries are (period, amplitude, phase,
declared amplitude).
Source code in src/popoto/backends/postgres/longtail.py
cyclic_columns(spec)
¶
State columns of every CyclicDecayField (role "state").
Source code in src/popoto/backends/postgres/longtail.py
safe_add(a, b)
¶
safe_div(a, b)
¶
a / b for b > 0 (or inf) that gives C's inf / 0
where Postgres would raise on overflow or underflow.
Source code in src/popoto/backends/postgres/longtail.py
cyclic_score_sql(ts, spec, field, *, now, rate, base_field, confidence_field, strength, confidence_partition=None)
¶
The CYCLIC_DECAY_LUA score of one row of ts (aliased t):
decayed + cyclic + pressure, evaluated in that order.
decayed is :func:~.memory.decay_score_sql -- the script's decay
and modulation steps are DECAY_SCORE_LUA's, and its unsplit base *
pow equals that script's sign * |base| * pow once + cyclic
(at least 0) has turned a -0 into +0. There is no validity
gate: the script has none (TestCyclicDecayGatingGap).
Source code in src/popoto/backends/postgres/longtail.py
cyclic_save_parts(ts, spec, obj, names)
¶
CYCLES_MERGE_LUA for each CyclicDecayField the save writes, as
upsert parts: the new row's columns, and ON CONFLICT expressions that
merge the declaration into the stored cycles -- period and phase from the
declaration, amplitude learned unless the declaration was edited (#698),
baseline = the declared amplitude -- and refresh the pressure rate,
keeping last_resolved (now for a new entry). No declared cycles
clears the cycles; pressure_rate <= 0 clears the pressure. None
when the save writes no cyclic field.