• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

ARCHIVE - *** NVIDIA GEFORCE RTX 3080 SERIES STOCK SITUATION *** - NO COMPETITOR DISCUSSION

Status
Not open for further replies.
On the whole queue problem, here's the word of a developer, and I'm pretty sure some of you are too and will be able to agree.

The TI department has a rough estimation on when this will be delivered, they just don't want to communicate because of all the reasons already said here, people would mass cancel. And it's also OK to say, hey, this will take about 2 weeks, we can wait if we know whereabouts it'll be delivered. But what I can't stand is the fact that there's been no mitigation plan while there's this 2 weeks. A simple SQL query could gather a list of ORDER ID per GPU MODEL with STATUS(confirmed,paid,cancelled) ordered by DATE, and give us a nice idea on where we stand, there's no personal data in this list, and each one of you know your ORDER ID, so you can just look up that. God sake it would take me few minutes to query such data, and they already have, as they were able to present data on how many people bought, and which card will have more availability, etc. They just don't want to present the data because truth be told, it'll be a mass cancellation of the pre-orders.

I think this is very dishonest to say the least.

Regarding some people that are worried about corona virus and their ability to actually have inter-department communication. COVID shouldn't interfere in that, most of the IT work was already internet-enabled, and no, OCUK is not running crazy to do deliveries, they are most likely waiting for shipments to come, sort, and distribute, and as we all know, GPUs are not being delivered(we're assuming by the lack of comms from Gibbo), so they are not that crazy overburden that they can't communicate with IT, they are more likely thinking in a strategy to address peoples bad sentiment without causing them to lose millions of pounds.

I hope this situation changes early next week, let's wait for proper comms, but things are definitely not looking great.

From @NikTheSHNIK's comments last night it sounds like they were still sorting out payment issues and going through the backlog of cancelation requests till Thursday, so honestly I can understand that being a blocker to launching whatever queue system they were working on (since a queue that gives wrong information is just going to create more issues than it solves)

Add into that the fact we were still processing payments and cancellations until yesterday (I was helping out but there was still webnotes to clear from days before) an individual order's queue position was changing hourly, therefore an accurate queue position was impossible to convey.

However, even if that caused delays, even if that is the reason the queue isn't ready yet... an official "this is why it isn't ready, these are the issues we need to fix before you can use it" rather than no info from anyone who knows the actual progress seems wrong. I get that making sure the data in the system is right, making sure it doesn't manage to breach GDPR through a bug or bad choice, or any of the other suggested reasons people have been posting might be creating issues. Anything customer facing, even if a simple query at it's core, ends up needing to be wrapped in pointless bows and ribbons. But they should be telling us why the "Few Days" we were told on Monday is looking to be at least a week.

Honestly, I think the biggest issue here is that while some of the staff, notably @Gibbo and @NikTheSHNIK have been making efforts to keep us updated it doesn't seem anyone has actually been given the hat of "Collect updates, summarise them, and post them once a day". We just have @Gibbo with what little stock info he has, @NikTheSHNIK with any sales/customer service stuff he knows/has overheard, and silence for any other teams. They need basically give someone the job of managing our expectations, which would likely reduce the demand on the webnote and phone customer service, and so be worth that person spending an hour of their shift a day just collecting the info, letting us know, and responding to a few questions.
 
Sorry i am a younger (less knowledegable) enthusiast, whats the difference in 470, 330 and 220's.. i understand that there are two types of capacitors for filtering the power.. and Nvidia reference suggests 4:2 ratio for them.. one of them is a smaller which is what companies have cheaped out (or maybe lack of chips from nvidia forced this)
Need to check parts by numbers myself to find specs and then compare them. If You want have a read here
https://twitter.com/eTeknix/status/1309832180298850306

a98b526179ec7f43d4a35c9a5c37f33c0159bc00.png
 
I posted they using 470 same as Gigabyte they "should" be better quality than 330's and 220's but that requires also check of VRM's quality how much extra filtering is needed. Also MSI got 5+1 configuration as You see

Worry not. I'm about to start digging in to parts catalogues to check differences between types used by different brands.

MSI Ventus are 220's on this guys card he bought at retail:
https://youtu.be/daQnNUH7B5I?t=401

Timestamped, it's brief but very clear image.
 
Hopefully they don't watch 2 mins of eteknix as they certainly are not experts...

I would stop now nevermind at 420 do something more interesting....
 
See I'd say they reported *A* problem with the caps. Not that it caused this particular problem or that there isn't another inherent problem. They just said they found a problem and changed their cap layout accordingly.

The way I see it (having never taken part in a card launch until now), is I'll take the card. If there's real problems it will be RMAable and they will need to solve it. If it's just "reduce the max boost a tiny bit" it'll be annoying that I'll lose 2fps or whatever, but not that bad.

But, that's just my take on it.
 
I'm not an OCUK fanboy, but I think the reality of the situation needs to be brought forward about this queue system. I'm a developer, with lots of web experience, too. Some things which people need to understand is that the 'unofficial queue' tracker is a basic python script uploaded onto a website running a virtual terminal. No one is liable when uploading data. However, OCUK are when developing their own system. The first matter: How complex is the order system? Seeing as the database is MySQL, what SQL queries are needed to first order customers, per card, per ETA, take away cancellations on updates, joining tables etc. You see? It's gets pretty complex, especially when security is paramount.

If OCUK released this queue system that started spitting out users full names, addresses and payment information due to that users relationship with the order number, then I'm sure people would be pretty angry. There is a reason people kept putting in their order numbers into the unofficial tracker without the last xx at the end, and that is privacy. OCUK do not want your details being leaked, breaching confidentiality which brings in the data protection act not to mention the ICO breathing down their ass for lack of planning and proper security implementation. Slapping some code together is the easy part. The hard part is IT governance and following internal and external policies for the safety of everyone's information.

However, why they didn't just mention something similar to this, I've no idea. My only speculation could be that they aren't doing any of that, and could be going old fashioned printing out a bunch of orders and firing them into MS Excel and simply using functions to calculate the first come first serve. Or, I'm completely wrong, and they're just really busy and don't have the time to explain it to marketing and CS. Every company has their own way of doing things, and my theory could be way off. I do think communication could be better from them, though. I think that is where people seem to be getting most angry. Sometimes Marketing/PR or even legal will stay quiet, since it's sometimes seen as the best option during botched launches like this where you might just keep digging yourself deeper.

No matter how complex is the system, and I can say because I worked on some complex distributed systems(and still do), there's always a low hanging fruit mitigation plan that can be done if the company is efficient, yes, there's a lot of things to consider, even legal department should be involved, but there will always be that small team of 2 or 3 very competent individuals that needs to enable a fast rolling plan to tackle "live operation is on fire" situation. Imagine they were this slow to tackle a situation where the payment system is actually infinitely charging credit card to the point it gets blocked, or the e-shop gets blocked, etc. Imagine 2 weeks to sort that out. They could even go bankrupt with this efficiency on issues critical like this.

If they really wanted, they could compile the so-called SQL list, like I stated before and also you did, and write a small program to send the queue position given the proper notice for an estimation of your position on the queue. And as many people pointed before, I prefer to receive regular updates that my ETA is pushed than not having any ETA at all, it builds up the anxiety which is another problem. As long it's all clear and properly worded, it should be fine. Or at least finer than it is right now.
 
I'm not an OCUK fanboy, but I think the reality of the situation needs to be brought forward about this queue system. I'm a developer, with lots of web experience, too. Some things which people need to understand is that the 'unofficial queue' tracker is a basic python script uploaded onto a website running a virtual terminal. No one is liable when uploading data. However, OCUK are when developing their own system. The first matter: How complex is the order system? Seeing as the database is MySQL, what SQL queries are needed to first order customers, per card, per ETA, take away cancellations on updates, joining tables etc. You see? It's gets pretty complex, especially when security is paramount.

If OCUK released this queue system that started spitting out users full names, addresses and payment information due to that users relationship with the order number, then I'm sure people would be pretty angry. There is a reason people kept putting in their order numbers into the unofficial tracker without the last xx at the end, and that is privacy. OCUK do not want your details being leaked, breaching confidentiality which brings in the data protection act not to mention the ICO breathing down their ass for lack of planning and proper security implementation. Slapping some code together is the easy part. The hard part is IT governance and following internal and external policies for the safety of everyone's information.

However, why they didn't just mention something similar to this, I've no idea. My only speculation could be that they aren't doing any of that, and could be going old fashioned printing out a bunch of orders and firing them into MS Excel and simply using functions to calculate the first come first serve. Or, I'm completely wrong, and they're just really busy and don't have the time to explain it to marketing and CS. Every company has their own way of doing things, and my theory could be way off. I do think communication could be better from them, though. I think that is where people seem to be getting most angry. Sometimes Marketing/PR or even legal will stay quiet, since it's sometimes seen as the best option during botched launches like this where you might just keep digging yourself deeper.

I think the most inexperienced dude in my company could have put together a way of seeing the queue position in the time it took you to write this message :)
It's a hyperbole, of course, but it's trivial. They surely have the orders centralized somewhere, along with the customer info and ordered items.
1) assume spamming/request quota/not logged in calls are handled by "framework"
2) if user trying to see queue position about a different user's order, quit
3) get SUM(quantity) of active orders with 3080 cards WHERE id <= user order id
4) push, merge, deploy

Wtf is possibly taking them days?
 
Hopefully they don't watch 2 mins of eteknix as they certainly are not experts...

I would stop now nevermind at 420 do something more interesting....
Not expected to see You posting here. Hope ya doing ok and Benching Hard art Gym and the Cards. . You have Hand's on Expirience with 3080's You got any conclusions. Once I get one Ill start to see what's the deal what can i do with and to it haha.
Also drop us something about them new waterblocks in watercooling section if ya got a minute still hyped to see what they turn up like :)
 
Mate, take a breather, genuinely, your recent posts have been very hard to understand, for example,

"Not Threatening been doing them for YEar's its 21 century i moved on fgrom keyboard wards to proper in face insults. Hurt's people More"

I'm sorry but this makes absolutely no sense to me, is this slang?

I'm not trying to attack or belittle you, but perhaps proof read your post before hitting submit, I have to do this myself quite often due to being dyslexic.

I have to read mine too due to taking sycdelix
 
Some like myself got nothing more interesting to do than sit on net waiting for new hardware. Been for 10km run and did 2 hour training today as it is :D
Atm car warming up in garage will go for flat out blast on b roads hopefully wont crash some driffting attemps :D

@8 Pack this topic will hit 500 pages by Wednesday EASY
 
Quick question in between all the feuds: we can cancel pre orders even after two weeks if they are not delivered correct? There is no time limit to cancel and get a full refund?
You can cancel SAME DAY you placed preorder on any part at OCUK takess few days to process money back think around 3 from personal experience while paying paypall.
 
Status
Not open for further replies.
Back
Top Bottom